Tim,

I'm not starting a new discussion on this topic, but I had hoped that you'd
reconsider (in ElevateDB) to enforce the general requirement that columns
referenced in the select list must either be contained in an aggregate
function or also specified in the GROUP BY clause.

Allowing ambiguous values in the result set is IMO kind of ugly.

Ole Willy Tuv

Ole,

<< I'm not starting a new discussion on this topic, but I had hoped that
you'd reconsider (in ElevateDB) to enforce the general requirement that
columns referenced in the select list must either be contained in an
aggregate function or also specified in the GROUP BY clause.

Allowing ambiguous values in the result set is IMO kind of ugly. >>

The jury is still out on this "feature".  For now I didn't want to break any
DBISAM queries for that rule simply because EDB doesn't require it.  Also,
due to the way EDB processes rows in the result set, any non-GROUP BY rows
will be associated with the value returned by a MIN() or MAX() operation, so
the result is a little more reliable than with DBISAM.

--
Tim Young
Elevate Software
www.elevatesoft.com