From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: To Postgres Devs : Wouldn't changing the select limit |
Date: | 2001-10-20 02:51:15 |
Message-ID: | 200110200251.f9K2pF427228@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> If you are confident that LIMIT #,# would never be an official SQL
> standard who am I to second guess that ;) I don't see that possibility
> anywhere either, but I just wanted to make sure. The possibility that it
> might become an official standard is the only objection I had against
> deprecating and eventual elimination of that syntax.
>
> LIMIT # OFFSET # has my vote.
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 there are other queries that use syntax that frequently fails, I
would like to hear about it so we can generate a helpful error message
rather than just a generic syntax error.
--
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 03:44:44 | Re: To Postgres Devs : Wouldn't changing the select limit |
Previous Message | Bruce Momjian | 2001-10-20 02:42:10 | Re: To Postgres Devs : Wouldn't changing the select limit |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-10-20 03:28:58 | Re: Detecting glibc getopt? |
Previous Message | Bruce Momjian | 2001-10-20 02:42:10 | Re: To Postgres Devs : Wouldn't changing the select limit |