RE: [PEAR] Re: [PEAR-DEV] Problems with PEAR::DB limitQuery
| From: | Lukas Smith | Date: | Mon, 08 Dec 2003 15:16:10 +0000 |
| Subject: | RE: [PEAR] Re: [PEAR-DEV] Problems with PEAR::DB limitQuery | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24269@lists.php.net to get a copy of this message | ||
> From: Jeroen Houben [mailto:jeroen@terena.nl]
> Sent: Monday, December 08, 2003 4:13 PM
> To: Alexey Borzov
> Alexey Borzov wrote:
>
> > Hi!
> >
> > Jeroen Houben wrote:
> >
> >> In older versions the LIMIT #, # *was* correct.
> >> From the postgresql changelog @
> >> http://developer.postgresql.org/~momjian/HISTORY.html
> >> (under
> >> migrating to 7.3) :
> >>
> >> Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce)
> >>
> >> So the class should do a version check and then execute the proper
> code.
> >> HTH,
> >
> >
> > The class should NOT do any version check, as LIMIT # OFFSET # syntax
> > is valid for all PostgreSQL versions, which is not true for LIMIT #,#.
> > Martin is right.
> >
> >
> I didn't know it was valid for *all* versions. In that case yes PEAR::DB
> should use LIMIT # OFFSET. I was under the impression that older
> versions 6.x (and even 7.0) could only work with LIMIT #,#.
Please open a bug report.
Regards,
Lukas