On Tue, 13 Jan 2004, David Teran wrote:
> I wonder if people encountered bugs like 'a select returns a wrong
> number of rows' or any other very serious bugs. We do not have problems
It's happened on rare occasion in the past in my recollection for things
that are basically bugs. It generally gets resolved quickly and usually
someone can suggest workaround SQL while waiting.
Nominally speaking, some of the case folding issues with identifiers might
be considered to be such a problem: Select * from FOO, "foo" meaning
something different when two tables were created as "FOO" and "foo" from
what the spec would want. This is currently considered a don't do it sort
of situation.
Umm, there are some things that aren't really done yet, for example IIRC
upper()/lower() really only work on single byte encodings. There are
probably other things of this sort that one might need to watch out for.
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
