From: | David Ford <david(at)blue-labs(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: To Postgres Devs : Wouldn't changing the select limit |
Date: | 2001-10-18 20:23:04 |
Message-ID: | 3BCF3A28.8080808@blue-labs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
I think that's a grand idea. Mysql does a lot of things in an 'odd' way
and I prefer the unambiguous LIMIT .. OFFSET form, it follows the design
of SQL in general.
-d
Bruce Momjian wrote:
>OK, it seems enough people don't want this change that we have to do
>something. What do people suggest? Can we throw an elog(NOTICE)
>message in 7.2 stating that LIMIT #,# will disappear in the next release
>and to start using LIMIT/OFFSET. That way, people can migrate their
>code to LIMIT/OFFSET during 7.2 and it can disappear in 7.3?
>
>I frankly think the LIMIT #,# is way too confusing anyway and would be
>glad to have it removed.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Hallstrom | 2001-10-18 21:02:22 | Re: To Postgres Devs : Wouldn't changing the select limit |
Previous Message | Russ McBride | 2001-10-18 20:10:47 | Re: drop column |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Hagerty | 2001-10-18 20:54:57 | Re: PQstatus() detect change in connection... |
Previous Message | Tom Lane | 2001-10-18 20:15:49 | Re: Create or replace function doesn't work so well |