User writes "ORDER BY y" and gets something not ordered by y, but rather by the DISTINCT's selection order on x, which can change from call to call based on activity on the tab table. That's what the user will get in the situation that x's map to multiple y's.
It's may be obvious what the user wanted (an ordered set on y), but not what the user will get (a random set on x). Perhaps I've not understood the concern here, but that seems like pretty "bad" SQL to me. A user is always empowered to request misleading data from a database, though. That's good marketing. > Anyway, I think it is completely obvious what the user wanted when he/ > she wrote the query. > >>> SELECT DISTINCT x FROM tab ORDER BY y; ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
