Re: To Postgres Devs : Wouldn't changing the select limit - Mailing list pgsql-general

From Bruce Momjian
Subject Re: To Postgres Devs : Wouldn't changing the select limit
Date
Msg-id 200110200251.f9K2pF427228@candle.pha.pa.us
Whole thread Raw
In response to Re: To Postgres Devs : Wouldn't changing the select limit  (Jochem van Dieten <jochemd@oli.tudelft.nl>)
Responses Re: To Postgres Devs : Wouldn't changing the select limit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> 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@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: speedboy
Date:
Subject: Re: phpPgAdmin 2.3 build broken?
Next
From: Bruce Momjian
Date:
Subject: Re: To Postgres Devs : Wouldn't changing the select limit