Re: To Postgres Devs : Wouldn't changing the select limit
От | Bruce Momjian |
---|---|
Тема | Re: To Postgres Devs : Wouldn't changing the select limit |
Дата | |
Msg-id | 200110172046.f9HKkTn07208@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: To Postgres Devs : Wouldn't changing the select limit (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: To Postgres Devs : Wouldn't changing the select limit
|
Список | 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 behaviour than to not follow > MySQL behaviour? Well, it was on the TODO list and people complained while porting their MySQL applications. We clearly made a mistake in the initial implementation. The question is do we fix it or continue with a different implementation. Because we have the separate LIMIT and OFFSET we can fix it while giving people a solution that will work for all versions. If we don't fix it, all MySQL queries that are ported will be broken. I assume it got on the TODO list because fixing it was the accepted solution. We can, of course, change our minds. -- 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 по дате отправления: