| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Flancer <huongch(at)bigfoot(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: To Postgres Devs : Wouldn't changing the select limit |
| Date: | 2001-10-17 22:34:34 |
| Message-ID: | 200110172234.f9HMYYM11991@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rdack | 2001-10-18 00:13:01 | can't create a database |
| Previous Message | Jason Earl | 2001-10-17 22:05:14 | Re: SQL equivallent to "\ds" in psql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Hagerty | 2001-10-18 00:47:09 | PQstatus() detect change in connection... |
| Previous Message | Dan | 2001-10-17 22:19:11 | Re: compiling libpq++ on Solaris with Sun SPRO6U2 (fixed |