|
|
Posted by Hugo Kornelis on 09/30/05 22:33
On 26 Sep 2005 10:20:36 -0700, Rick wrote:
>I'm not so sure it isn't a bug.
>Here are some observations.
>If I write a select statement like
>'Select * from mytable order by datecolumn, intcolumn', the int column
>order is correct.
>If I write a select statement like
>'Select * from mytable order by datecolumn desc, intcolumn', the int
>column order is not correct.
>This parallels the (mis) behaviour of the clustered index.
>Is there a logical reason for this or is this a bug?
Hi Rick,
If you include the ORDER BY clause, the results should be in the
requested order. Anything else would be a bug. But first: what program
are you using to run these queries? How does that program display the
values from the date column - are hours, minutes, seconds and
milliseconds included? Becuase they ARE considered in the sort
operation; if they are then cut-off in the display of your client
program, the results might APPEAR to be ordered incorrectly. If you're
unsure, re-run the query using Query Analyzer.
If that doesn't help, then I'd very much like to see a repro script,
consisting of CREATE TABLE statements, some INSERT statements to set up
the data and the SELECT statements that cause the suspected buggy
behaviour. See www.aspfaq.com/5006.
Also, include the output of SELECT @@VERSION in your next post, please.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)
Navigation:
[Reply to this message]
|