| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, rihad <rihad(at)mail(dot)ru>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: any way for ORDER BY x to imply NULLS FIRST in 8.3? |
| Date: | 2007-11-07 15:05:33 |
| Message-ID: | 20071107150533.GC26157@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 07, 2007 at 02:37:41PM +0000, Simon Riggs wrote:
> Editing an application, you would be required to add the words NULLS
> FIRST to every single ORDER BY and every single CREATE INDEX in an
> application. If we know that is what people would do, why not have one
> parameter to do this for them?
I find it hard to beleive that every single query in an application
depends on the ordering of NULLs. In fact, I don't think I've even
written a query that depended on a particular way of sorting NULLs. Is
it really that big a deal?
> Implement SQLServer and MySQL behaviour? Now we're talking about
> hundreds of new applications that might decide to migrate/support
> PostgreSQL because of our flexibility in being able to support both
> kinds of sorting.
TBH I think long term is should be attached to each column, as it is a
property of the collation (my COLLATE patch let you specify it per
column).
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Those who make peaceful revolution impossible will make violent revolution inevitable.
> -- John F Kennedy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2007-11-07 15:13:17 | Re: prepared statements suboptimal? |
| Previous Message | Gauthier, Dave | 2007-11-07 15:03:24 | Temporary, In-memory Postgres DB? |