Op 23 dec 2013, om 14:32 heeft Simon Slavin het volgende geschreven:
General note: when making up a name for a calculation like 'depth',
try to make sure it's not the name of any of the columns in the
tables mentioned in your SELECT. This avoids ambiguity.
. See if you can make the simplest possible SELECT that comes up
with unexpected results.
select 0 as depth
from (select 1 as depth)
group by null
having depth < 1
;
This returns no rows. Thus the HAVING clause refers to the depth from
the FROM part, not that in the SELECT part. May this be what is
causing the unexpected result?
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
