From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: To Postgres Devs : Wouldn't changing the select limit |
Date: | 2001-10-18 18:18:34 |
Message-ID: | 24899.1003429114@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> writes:
> I would say the relevant behaviour is neither the one that MySQL
> historically uses nor the one that PostgreSQL historically uses, but the
> one that is specified in the relevant standards.
There aren't any: SQL92 and SQL99 have no such feature. (Although I
notice that they list LIMIT as a word likely to become reserved in
future versions.)
AFAIK we copied the idea and the syntax from MySQL ... but we got the
order of the parameters wrong.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Earl | 2001-10-18 18:19:06 | Re: newbie authentication/automated backup (pg_dumpall) questions |
Previous Message | Keary Suska | 2001-10-18 18:12:14 | Re: newbie authentication/automated backup (pg_dumpall) |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Coffman | 2001-10-18 18:33:06 | VACUUM vs VACUUM ANALYZE |
Previous Message | Tom Lane | 2001-10-18 18:10:19 | Re: PQstatus() detect change in connection... |