From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit |
Date: | 2001-10-22 05:51:42 |
Message-ID: | 3BD3B3EE.CD7B22D1@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> > > 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.
> > 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.
> OK, we have received only one vote to keep LIMIT #,# working for one
> more release, and several to remove it so I am committing a patch now to
> remove LIMIT #,# and instead have them use LIMIT # OFFSET #:
I've cc'd this to the hackers list. I know the discussion started on
general, but if I hadn't been subscribed to *that* list I'd have never
known about any of this. And noone else on hackers would either.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-10-22 05:56:54 | Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit |
Previous Message | Alvaro Herrera | 2001-10-22 05:13:43 | Database corruption? |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-10-22 05:56:54 | Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit |
Previous Message | speedboy | 2001-10-22 05:24:28 | createlang difficulty. |