Thread: Global setting for ORDER BY ... NULLS FIRST / LAST
Hello!
Is there a global PostgreSQL server setting or SQL session parameter that defines the default for ORDER BY ... NULLS FIRST / LAST ?
Assuming that it would be something like "NULL is lowest value, or NULL is highest value", to get the expected behavior when using ASC/DESC options of ORDER BY ...
That would help to migrate to PostgreSQL for DB engines having a different default behavior regarding NULL sorting.
Thanks!
Seb
On Tue, Mar 1, 2022 at 7:16 AM Sebastien Flaesch <sebastien.flaesch@4js.com> wrote:
Is there a global PostgreSQL server setting or SQL session parameter that defines the default for ORDER BY ... NULLS FIRST / LAST ?
Nope
Assuming that it would be something like "NULL is lowest value, or NULL is highest value", to get the expected behavior when using ASC/DESC options of ORDER BY ...
I don't think I quite follow the above, but may I suggest you read our excellent documentation on how the feature presently functions before making suggestions on how to change it.
That would help to migrate to PostgreSQL for DB engines having a different default behavior regarding NULL sorting.
IMO, not enough of a benefit to spend development time on. Having global configuration like this is something that should be, and in general is, avoided. Most of the exceptions to this have been regretted.
David J.
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tue, Mar 1, 2022 at 7:16 AM Sebastien Flaesch <sebastien.flaesch@4js.com>
> wrote:
>> Is there a global PostgreSQL server setting or SQL session parameter that
>> defines the default for ORDER BY ... NULLS FIRST / LAST ?
> IMO, not enough of a benefit to spend development time on. Having global
> configuration like this is something that should be, and in general is,
> avoided. Most of the exceptions to this have been regretted.
Yeah. We have generally found that settings that change query semantics
are a net evil.
regards, tom lane
OK I understand.
Seb
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Tuesday, March 1, 2022 4:02 PM
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Subject: Re: Global setting for ORDER BY ... NULLS FIRST / LAST
Sent: Tuesday, March 1, 2022 4:02 PM
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-sql <pgsql-sql@lists.postgresql.org>
Subject: Re: Global setting for ORDER BY ... NULLS FIRST / LAST
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tue, Mar 1, 2022 at 7:16 AM Sebastien Flaesch <sebastien.flaesch@4js.com>
> wrote:
>> Is there a global PostgreSQL server setting or SQL session parameter that
>> defines the default for ORDER BY ... NULLS FIRST / LAST ?
> IMO, not enough of a benefit to spend development time on. Having global
> configuration like this is something that should be, and in general is,
> avoided. Most of the exceptions to this have been regretted.
Yeah. We have generally found that settings that change query semantics
are a net evil.
regards, tom lane
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tue, Mar 1, 2022 at 7:16 AM Sebastien Flaesch <sebastien.flaesch@4js.com>
> wrote:
>> Is there a global PostgreSQL server setting or SQL session parameter that
>> defines the default for ORDER BY ... NULLS FIRST / LAST ?
> IMO, not enough of a benefit to spend development time on. Having global
> configuration like this is something that should be, and in general is,
> avoided. Most of the exceptions to this have been regretted.
Yeah. We have generally found that settings that change query semantics
are a net evil.
regards, tom lane