Bug 84460

Summary: pear/DB/pgsql.php incompatible with postgresql 7.3
Product: [Retired] Red Hat Linux Reporter: Marco Pratesi <marco>
Component: phpAssignee: Joe Orton <jorton>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: marius.andreiana
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-07-03 11:46:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marco Pratesi 2003-02-17 18:49:37 UTC
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:
http://cvs.php.net/diff.php/pear/DB/DB/pgsql.php?login=2&r1=1.12&r2=1.13&ty=h

Marco Pratesi


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


How reproducible:
Always

Steps to Reproduce:
1. Use the PEAR DB limitQuery() method with postgresql 7.3
2.
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 21:32:02 UTC
Thanks for the report, this will be fixed in the next erratum.

Comment 2 Joe Orton 2003-07-03 11:46:46 UTC
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.

http://rhn.redhat.com/errata/RHSA-2003-204.html