Subject Re: Query returning row when it shouldn't...
Author Roman Rokytskyy
> That's a good point (that you should get one and exactly one
> result).... but is this correct when there are zero rows to start
> with? Shouldn't this be reflected by the agregate function returning
> zero rows? :-)

No, see my reply in Firebird-Support group. When MAX() is used with
empty relation, its result is NULL value, not an empty one.

Roman