Subject | Re: [firebird-support] Re: Valid reasons for sorting on a column one doesn't select? - a BUG! |
---|---|
Author | Grant Brown |
Post date | 2005-08-14T11:17:38Z |
No way is that a bug
SELECT First_Name, Last_Name
FROM Employee
ORDER BY Employer // just want the names not the employer
SELECT First_Name, Last_Name
FROM Employee
ORDER BY State_Lived_in // just want there names not the state the live in
is that not valid.
I could think of hundreds of querys like these and they are all valid.
To call that a bug in IMO is not correct.
To make things even worse, what happens when the query is run across the
wire. If it was a bug would you not be forcing un-necessary wire traffic
just so you can see what column you sorted on
Does not compute and allowing it makes the SQL code much more flexible.
--
Regards,
Grant Brown
Product Development Manager
Phone : 02 4229 1185
Mobile : 0412 926 995
Email : grant@...
Web : www.sitedoc.com.au
SiteDoc - Easy to Use - Powerful Results
SELECT First_Name, Last_Name
FROM Employee
ORDER BY Employer // just want the names not the employer
SELECT First_Name, Last_Name
FROM Employee
ORDER BY State_Lived_in // just want there names not the state the live in
is that not valid.
I could think of hundreds of querys like these and they are all valid.
To call that a bug in IMO is not correct.
To make things even worse, what happens when the query is run across the
wire. If it was a bug would you not be forcing un-necessary wire traffic
just so you can see what column you sorted on
Does not compute and allowing it makes the SQL code much more flexible.
--
Regards,
Grant Brown
Product Development Manager
Phone : 02 4229 1185
Mobile : 0412 926 995
Email : grant@...
Web : www.sitedoc.com.au
SiteDoc - Easy to Use - Powerful Results