|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #80340 PDO incorrectly parses string literals for platforms other than MySQL
Submitted: 2020-11-08 19:31 UTC Modified: 2020-11-08 21:35 UTC
From: morozov at tut dot by Assigned: cmb (profile)
Status: Duplicate Package: PDO Core
PHP Version: 7.4.12 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
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:
Solve the problem:
40 - 27 = ?
Subscribe to this entry?

 [2020-11-08 19:31 UTC] morozov at tut dot by
When extracting prepared statement parameters, the SQL parser doesn't take into account the dialect of the currently used database platform.

Specifically, it unconditionally expects string literals to use backslash for escaping the closing delimiter (single or double quote), although it's only supported by MySQL. It causes incorrect query parsing on other platforms (e.g. PostgreSQL).

In the following script, the parser interprets the combination of the backslash and the quote as part of the literal, so the following question mark gets replaced with the $1 placeholder, however, it should remain intact as part of the literal.

Test script:
$conn = new PDO('pgsql:...');

$sql = <<<'SQL'
SELECT '\'', ?'

$stmt = $conn->prepare($sql);

Expected result:
postgres=# SELECT '\'', ?';
 \', ?
(1 row)

Actual result:
\', $1


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2020-11-08 21:35 UTC]
-Status: Open +Status: Duplicate -Assigned To: +Assigned To: cmb
 [2020-11-08 21:35 UTC]
Duplicate of bug #79276.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Jul 14 23:01:30 2024 UTC