At 16:56 +0200 2/6/03, monty@stripped wrote:
>Below is the list of changes that have just been committed into a local
>4.0 repository of monty. When monty does a push these changes will
>be propagated to the main repository and, within 24 hours after the
>push, to the public repository.
>For information on how to access the public repository
>see http://www.mysql.com/doc/I/n/Installing_source_tree.html
>
>ChangeSet
> 1.1560 03/02/06 16:55:59 monty@stripped +19 -0
> Added START TRANSACTION syntax
> Added ALL as parameter option for all group functions.
> Make join handling uniform. This allows us to use ',', JOIN and
>INNER JOIN the same way.
> Sort NULL last if DESC is used (ANSI SQL 99 requirement)
Okay, way back, NULL sorted first by default and last if DESC was given.
Then in 4.0.2, it was changed so that NULL sorted first whether or not
DESC was given:
>@node News-4.0.2, News-4.0.1, News-4.0.3, News-4.0.x
>@appendixsubsec Changes in release 4.0.2 (01 Jul 2002)
>
>
>@item
>Use @code{ORDER BY column DESC} now sorts @code{NULL} values first.
>(In other words, @code{NULL} values sort first in all cases, whether or
>not @code{DESC} is specified.)
I thought that change was made for ANSI-behavior reasons?
Now, NULL is once again supposed to sort last with DESC ... for ANSI behavior?
I don't get it. What's going on? These flip-flops in behavior
are confusing.
