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 200110190126.f9J1QHn10265@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>)
List pgsql-general
> But according to the list in the PostgreSQL docs OFFSET is not a
> reserved word. Is it one of the 'likely to become reserved' words?
>
>
> > IMHO "LIMIT n OFFSET n" is far more readable than "LIMIT m,n" anyway.
> > (Quick: which number is first in the comma version?  By what reasoning
> > could you deduce that if you'd forgotten?)  So I think we should
> > deprecate and eventually eliminate the comma version, if we're not
> > going to conform to the de facto standard for it.
>
>
> I agree that LIMIT n OFFSET n is by far the most readable format, and is
> therefore the desirable format. But I am not sure about deprecating and
> eliminating the other syntax. Above all it should be avoided that it is
> now deprecated but is included in the next SQL standard and has to be
> added again.

I am confused.  While LIMIT and OFFSET may are potential SQL standard
reserved words, I don't see how LIMIT #,# would ever be a standard
specification.  Do you see this somewhere I am missing.  Again, LIMIT
#,# is the only syntax we are removing.

--
  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: Tom Lane
Date:
Subject: Re: To Postgres Devs : Wouldn't changing the select limit
Next
From: Tom Lane
Date:
Subject: Re: VACUUM vs VACUUM ANALYZE