From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: To Postgres Devs : Wouldn't changing the select limit |
Date: | 2001-10-20 04:54:41 |
Message-ID: | 200110200454.f9K4sfl04755@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > One more thing. I have added the code to suggest alternate syntax for
> > LIMIT #,#:
>
> > test=> select * from pg_class LIMIT 1,1;
> > ERROR: LIMIT #,# syntax no longer supported. Use LIMIT # OFFSET #.
>
> If you're going to do that, *please* suggest the *correct* substitution.
> AFAICT, our version of LIMIT m,n transposes to OFFSET m LIMIT n; but
> your message suggests the opposite.
Remember, the 7.1 code was:
! select_limit: LIMIT select_limit_value ',' select_offset_value
! { $$ = makeList2($4, $2); }
This was changed a few weeks ago to match MySQL, and only today removed.
However, our new message suggests the old PostgreSQL syntax, not the
MySQL syntax. Optimally we should ship with this ordering for 7.2 and
reverse it for 7.3 or 7.4.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-10-20 05:01:47 | Re: To Postgres Devs : Wouldn't changing the select limit |
Previous Message | Tom Lane | 2001-10-20 03:44:44 | Re: To Postgres Devs : Wouldn't changing the select limit |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-10-20 05:01:47 | Re: To Postgres Devs : Wouldn't changing the select limit |
Previous Message | Joel Burton | 2001-10-20 04:22:30 | Re: Catalogs design question |