Greetings, Bruce!
At 18.10.2001, 02:34, you wrote:
>> Isn't it much worse to not follow PostgreSQL behavior than to not follow
>> MySQL behavior?
BM> Another idea: because our historical Limit #,# differs from MySQL, one
BM> idea is to disable LIMIT #,# completely and instead print an error
BM
Bruce Momjian wrote:
>>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 m
Bruce Momjian wrote:
>
> > 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.
> 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 foll
> 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 foll
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 beha
Break the SQL code that has been implemented for prior versions??
Bummer ;((.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster