Subject | Re: [firebird-support] Re: How to mix ascending and descending fields in one index |
---|---|
Author | Nico Callewaert |
Post date | 2009-10-09T07:29:45Z |
Well,
The truth is that there are a lot of rude answers passing here, like "Hire a programmer", just to name one. Or all kind of short and unpleasant remarks. I think that is not nice for anybody. One cannot assume that all others has the same level of experience or knowledge...
Just my 10 cents,
N.
The truth is that there are a lot of rude answers passing here, like "Hire a programmer", just to name one. Or all kind of short and unpleasant remarks. I think that is not nice for anybody. One cannot assume that all others has the same level of experience or knowledge...
Just my 10 cents,
N.
----- Original Message -----
From: Valeri Mytinski
To: firebird-support@yahoogroups.com
Sent: Friday, October 09, 2009 9:17 AM
Subject: Re: [firebird-support] Re: How to mix ascending and descending fields in one index
Can I tell my very personal opinion about this list, FB, and "what to do"?
I use FB about a year. Before (in fifteen years) I used Informix, MySQL,
Sybase, Postrgresql, MsSql. FB is worst. I spend much time on finding tricks
and workarounds. Some things just don't work as they must do (for example,
constraints).
Why I rarely ask my questions to this list? One cause is I don't like
answers like:
> Everybody with even a vague recollection of a computer science
> course knows...
or
> If people are really serious about arguing a case for a
> feature enhancement or a re-implementation, they should
> do it in firebird-architect or firebird-devel...
As almost all unconditional statements in world these are not truth
and first is also rude
(for me).
And I don't like to read 10 those in hope that 11's will be answer to
my question.
And it's most annoying to see such answers from developers or managers
or experts.
I think that weakest point of FB now is lack of good documentation.
I would like to see something like PostgreSQL manual. Documentation
must be full for
every release. I want to find ALL of FB's syntax, options, udf etc. in
the documentation
that comes with release. I don't like answers in this list like "see
Release notes for version xxx".
Documentation must be actual - all must work like documentation states
and vise versa.
I think that such documentation is even more important than new major releases.
I would prefer good documentation and new features in last stable
release than new release.
New release is additional work to my project: may be some code must be
rewritten,
all must be retested, and all customer's installations must be upgraded.
Regards
Valeri
[Non-text portions of this message have been removed]