Subject | Re: Query returning row when it shouldn't... |
---|---|
Author | phil_sorry_trouble_with_profile |
Post date | 2004-05-31T21:32:49Z |
--- In firebird-support@yahoogroups.com, "Roman Rokytskyy"
<rrokytskyy@y...> wrote:
SQL standard - (a distant cousin :-) ) so not quite so definitive as
the spec itself - and the footnote reads "This document was written
originally by Wang Lam for Prof. Jennifer Widom's CS145 class, Spring
2003".
Regardless, I agree that the SQL when run as-is should return null.
But what is the *correct* behaviour under Java/JDBC? This is mainly
for my own sanity, afterall I have to work with whatever's out there!
<rrokytskyy@y...> wrote:
> > That is encouraging but that link is not an official specification?Actually, the web page appears to be *extracts* from a *guide* to the
>
> That's C. J. Date and Hugh Darwen A Guide to the SQL Standard. Fourth
> edition, Addison-Wesley, Reading, Massachusetts, 1997. (ISBN
> 0-201-96426-0). SQL standard does not mention explicitly this issue
> (at least I was not able to find it in SQL 99 standard).
SQL standard - (a distant cousin :-) ) so not quite so definitive as
the spec itself - and the footnote reads "This document was written
originally by Wang Lam for Prof. Jennifer Widom's CS145 class, Spring
2003".
Regardless, I agree that the SQL when run as-is should return null.
But what is the *correct* behaviour under Java/JDBC? This is mainly
for my own sanity, afterall I have to work with whatever's out there!