--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:

> > I don't know what grokking is,
>
> "grok" - To understand profoundly through intuition or empathy.
> (Coined by Robert A. Heinlein in his Stranger in a Strange Land)
>
> > This is valid, expected behaviour in an SQL sense, but I hesitate to
> > agree that jdbc/java should wrap this perfectly 'as-is' without
> > attempting to do something better with it.
> > Maybe I *have* been living in a dreamworld working with SQLserver
> > for the last 2 projects ;-)
>
> I wouldn't call it dreamworld, but rather MS world. This issue is not
> described by the standard, and if we implement it the way MS does,
> that would break other application that rely on the standard and the
> fact that JDBC driver does not do any interpretation of the result
> set. Microsoft tends to ignore standards, we don't.

Cool... I usually eschew microsoft products, I don't use IE or
outlook, believe in the w3c, and contribute towards open source... ;-)
I think maybe in the last couple of projects (where I've used max(...)
more than usual) I've got used to what is probably a quirk in the JDBC
driver I used. I've spoken to others who haven't seen this with
SQLserver - or at least haven't realised it.

Thanks