|
|
Posted by David Portas on 03/08/06 20:14
RickW wrote:
> David Portas wrote "... then what if the ORDER BY clause on the base
> view changes?"
>
> If it changes, it changes, and you (or at least I) would hope that the
> designer in charge of the base view would understand that design changes
> of that nature should come in response to user request, formal review,
> and acceptance of the effect, not in silence just because the designer
> felt like it.
>
> I don't think that this possibility supports your argument.
>
> *** Sent via Developersdex http://www.developersdex.com ***
I agree with you. My principal objection is not that ordering views
makes change management harder (although it must do to some degree). My
argument is that for it to work the users must be aware of what
ordering exsits in the view and must take account of that when
designing their queries. So in my opinion there is no usability benefit
to be had from an ordered view other than saving the time it takes to
type in the column names.
If saving keystrokes is your goal then more benefit could be obtained
from creating a better development environment. I'm talking about
features like the object browser in Management Studio that save you
from typing lists of column names.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|