|
|
Posted by RickW on 03/23/06 07:59
Erland wrote <If you need a certain order from a query, you need to use
ORDER BY.>
We all know that you need to use ORDER BY. We just thought it should be
available in a query stored as a view in SQL Server.
By the way, across 8 years of SQL Server 7/2000 use, I never had an
instance of using ORDER BY in a view that failed to return an ordered
record set.
Obviously I need someone to explain why, if it's okay to use ORDER BY in
a query to get an ordered data set, it's not okay to store that query as
a view in a tool like SQL Server and see that ordered result in my
application, without having to write a query from the application.
I agree with Herb. It was lazy of Microsoft to omit a solution to this.
I'm lucky. I have one application of 60K lines of VB, and only about 30
views relied on ORDER BY to present ordered data to the application.
Moving the ORDER BY to the application side was not a big deal for our
app. I can sure see how a lot of developers could be in a much worse
situation.
Science is organized common sense where many a beautiful theory was
killed by an ugly fact. -- Thomas Huxley
*** Sent via Developersdex http://www.developersdex.com ***
Navigation:
[Reply to this message]
|