> But that's past. It's mighty close to beta -- is this fix a showstopper? > The behavior currently is rather broken according to the results of the > discussion on general. Do we really want a whole 'nother major version cycle > to pass before this kludge is fixed? Six months to a year down the road? > > The longer this behavior is in the code, the harder it's going to be to > remove it, IMNSHO.
We just have too many opinions here. I have put it back and noted it will be removed in 7.3. If someone else wants to propose it to be removed in 7.2 and have a vote, and do the work, and take the heat, go ahead. I am not going to do it. It is just like the grief I got over jdbc patches for 7.1. At some point it is not worth having people get upset at me over it. Basically, you have removed any desire I have to resolve this. FYI, my personal opinion is that we should keep it around for one more release because forcing people to remove it from the queries with no warning is more disruptive, I think, than the fact we don't match MySQL's syntax. Also, LIMIT #,# is no longer documented. That change will be in 7.2. Of course, that means that if someone tries MySQL's syntax, they have no documentation stating that the params are backwards. If they read the HISTORY file, they will know not to use LIMIT #,# anyway. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
