Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-24 Thread Bruce Momjian
> Bruce Momjian writes: > > > I recommend tips when they are one line in length, have a high > > probability of being accurate, and are common mistakes. Anything longer > > and we should point to a specific section in the docs. > > I would put "when porting from MySQL" into that category. I wo

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-23 Thread Peter Eisentraut
Bruce Momjian writes: > I recommend tips when they are one line in length, have a high > probability of being accurate, and are common mistakes. Anything longer > and we should point to a specific section in the docs. I would put "when porting from MySQL" into that category. -- Peter Eisentra

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-22 Thread Tom Lane
Thomas Lockhart <[EMAIL PROTECTED]> writes: > I'm with Peter on this one. I'd like to *not* clutter up the code and > error reporting with hints and suggestions which may or may not be to > the point. > We *should* have docs which list error messages and possible solutions, > and throwing that inf

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-22 Thread Bruce Momjian
> Thomas Lockhart <[EMAIL PROTECTED]> writes: > > I'm with Peter on this one. I'd like to *not* clutter up the code and > > error reporting with hints and suggestions which may or may not be to > > the point. > > We *should* have docs which list error messages and possible solutions, > > and throw

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-22 Thread Thomas Lockhart
(switched thread to hackers) > ... If the 'tip' is localized to a few lines, usually in > gram.y, I don't see a reason not to help people find the right answer. > It helps them and reduces redundant bug repots. I can't imagine a > reason not to do it unless it starts to make our code more comple

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-22 Thread Bruce Momjian
> (switched thread to hackers) > > > ... If the 'tip' is localized to a few lines, usually in > > gram.y, I don't see a reason not to help people find the right answer. > > It helps them and reduces redundant bug repots. I can't imagine a > > reason not to do it unless it starts to make our code

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-22 Thread Bruce Momjian
> > > > I am confused. While LIMIT and OFFSET may are potential SQL standard > > > > reserved words, I don't see how LIMIT #,# would ever be a standard > > > > specification. Do you see this somewhere I am missing. Again, LIMIT > > > > #,# is the only syntax we are removing. > > > If you are co

Re: [HACKERS] [GENERAL] To Postgres Devs : Wouldn't changing the select limit

2001-10-22 Thread Thomas Lockhart
> > > I am confused. While LIMIT and OFFSET may are potential SQL standard > > > reserved words, I don't see how LIMIT #,# would ever be a standard > > > specification. Do you see this somewhere I am missing. Again, LIMIT > > > #,# is the only syntax we are removing. > > If you are confident th