I am not disagreeing about what the user wanted, and yes it is nit picking, but my feeling is that the DB guys have been at this alot longer than EJB-QL and EJB-QL should be the object version of SQL99. If that is the case either you modify the EJB-QL spec of say no you can not do this because SQL99 says so.
This is really a small drop in the bucket but really it is the underlying intent that is important. If EJB-QL=SQL99 then my answer is no, you can't do it. Otherwise you are going to have to discover all of the exception cases that the SQL spec has accounted for. On Tue, 2003-02-11 at 14:56, Dain Sundstrom wrote: > Dave that is not what I said. In the case that there happens to be two > rows with the same x value and different y values, I don't care. > Otherwise I do. > > Bases on what you have posted, how do you think we should handle this > case in EJB land? Should we just throw an error saying too bad? One > of the big short comings of EJB-QL is you can't select more then one > field. We will be adding a the ability to select multiple columns to > JBossQL in JB4, but what should we do in the mean time, and how should > we treat this for EJB-QL in JB4? > > Anyway, I think it is completely obvious what the user wanted when he/ > she wrote the query. > > -dain > > On Monday, February 10, 2003, at 08:24 PM, Dave Smith wrote: > > > If you do not care how it is ordered then why bother with the order by > > clause? The database is correct , you are not. > > > > Dain Sundstrom wrote: > > > >> > >> On Monday, February 10, 2003, at 01:53 PM, Dave Smith wrote: > >> > >>> No, it isn't. Consider > >>> > >>> SELECT DISTINCT x FROM tab ORDER BY y; > >>> > >>> Assuming there are multiple values of y for any given x, how would > >>> you > >>> expect the result to be sorted? It's ill-defined. > >> > >> > >> There is nothing ill defined by this. You want all of the distinct > >> entries of x ordered by y. If two x values have the different y > >> values. I simply don't care which one you choose to order by. Sure > >> you can get non deterministic results, but there is enough > >> information to execute the query. > >> > >> -dain > >> > >> > >> > >> ------------------------------------------------------- > >> 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 > > > > > > > > > > ------------------------------------------------------- > > 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 > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- 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
