Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit
Дата
Msg-id 200110221700.f9MH0FF02975@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: [GENERAL] To Postgres Devs : Wouldn't changing the select limit  (Thomas Lockhart <lockhart@fourpalms.org>)
Список 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.

The discussion has moved from patches to general so our general users
could comment on this.

--  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,
Pennsylvania19026
 


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Serguei Mokhov"
Дата:
Сообщение: Re: namespaces
Следующее
От: "Johann Zuschlag"
Дата:
Сообщение: Re: Error while restoring database