Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 84460 - pear/DB/pgsql.php incompatible with postgresql 7.3
pear/DB/pgsql.php incompatible with postgresql 7.3
Product: Red Hat Linux
Classification: Retired
Component: php (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-02-17 13:49 EST by Marco Pratesi
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-03 07:46:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2003:204 normal SHIPPED_LIVE : Updated PHP packages are now available 2003-07-02 00:00:00 EDT

  None (edit)
Description Marco Pratesi 2003-02-17 13:49:37 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021128

Description of problem:
The method modifyLimitQuery() does not work with postgresql 7.3,
as postgresql 7.3 does not support anymore the syntax "LIMIT #,#".
The problem would not be fixed upgrading to PHP 4.3.0.
To fix the problem, a patch from the CVS (fix done after the release
of PHP 4.3.0) is needed:

Marco Pratesi

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Use the PEAR DB limitQuery() method with postgresql 7.3

Actual Results:  postgresql returns an error:
ERROR:  LIMIT #,# syntax not supported.
        Use separate LIMIT and OFFSET clauses.

Expected Results:  The modifyLimitQuery() method should prepare for the postgresql
backend a query using separate LIMIT and OFFSET clauses.

Additional info:
Comment 1 Joe Orton 2003-06-12 17:32:02 EDT
Thanks for the report, this will be fixed in the next erratum.
Comment 2 Joe Orton 2003-07-03 07:46:46 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.