Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.5.0b5

Bug #13811 _skipDelimitedStrings bug
Submitted: 2008-04-30 19:46 UTC
From: alec Assigned: quipo
Status: Closed Package: MDB2
PHP Version: 5.2.5 OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 49 - 29 = ?

 
 [2008-04-30 19:46 UTC] alec (Aleksander Machniak)
Description: ------------ When use query e.g. UPDATE table SET col='' WHERE ... with postgresql driver function returns error: MDB2 Error: syntax error (-2): _skipDelimitedStrings: [Error message: query with an unterminated text string specified] I'm not sure if problem is in $string_quoting definition in postgres driver or in _skipDelimitedString(), but all works fine when I replace: } while ($ignore['escape'] && $query[($end_quote - 1)] == $ignore['escape']) with: } while ($ignore['escape'] && $query[($end_quote - 1)] == $ignore['escape'] && $end_quote-1 != $start_quote)

Comments

 [2008-05-01 06:49 UTC] alec (Aleksander Machniak)
Of course $string_quoting is defined properly, so problem is in _skipDelimitedStrings()
 [2008-05-03 04:40 UTC] doconnor (Daniel O'Connor)
Aleksander, can you provide a short script to reproduce this properly?
 [2008-05-03 08:17 UTC] alec (Aleksander Machniak)
$options = array(); $dsn = 'pgsql://dbuser:pass@192.168.0.100/dbname'; $query = "UPDATE identities SET signature='' WHERE identity_id=?"; $mdb2 =& MDB2::factory($dsn, $options); if (PEAR::isError($mdb2)) { die($mdb2->getMessage()); } $q = $mdb2->prepare($query); if (PEAR::isError($q)) { die($q->getMessage()); } $mdb2->disconnect();
 [2008-05-03 12:14 UTC] quipo (Lorenzo Alberton)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.