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 200110172234.f9HMYYM11991@candle.pha.pa.us
Whole thread Raw
In response to Re: To Postgres Devs : Wouldn't changing the select limit  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: To Postgres Devs : Wouldn't changing the select limit  (Alexey Borzov <borz_off@rdw.ru>)
List pgsql-general
> Bruce Momjian writes:
>
> > > Break the SQL code that has been implemented for prior versions??
> > >  Bummer ;((.
> >
> > Yes, but we don't follow the MySQL behavior, which we copied when we
> > added LIMIT.  Seems we should agree with their implementation.
>
> Isn't it much worse to not follow PostgreSQL behavior than to not follow
> MySQL behavior?

Another idea:  because our historical Limit #,# differs from MySQL, one
idea is to disable LIMIT #,# completely and instead print an error
stating they have to use LIMIT # OFFSET #.  Although that would break
both MySQl and old PostgreSQL queries, it would not generate incorrect
results.

--
  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: Jason Earl
Date:
Subject: Re: SQL equivallent to "\ds" in psql
Next
From: "Andrew Crouch"
Date:
Subject: Large Files?