Null normalizes to 'f' when PDO::ATTR_EMULATE_PREPARES = true
Open
Nobody has claimed this yet.
Bug
Extension: pdo_pgsql
Status: Needs Triage
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
The following code:
<?php
$pdo = new PDO(
'pgsql:host=localhost;port=5432;dbname=test',
'postgres',
'postgres',
[
PDO::ATTR_EMULATE_PREPARES => true,
],
);
/** @var PDOStatement $stmt */
$stmt = $pdo->prepare('SELECT :bool_val as bv');
$stmt->bindValue(':bool_val', null, PDO::PARAM_BOOL);
$stmt->execute();
foreach ($stmt->getIterator() as $item) {
var_dump($item['bv']);
}
Resulted in this output:
string(1) "f"
But I expected this output instead:
NULL
When ATTR_EMULATE_PREPARES not used, NULL is actually returned.
PHP Version
PHP 8.2.11
Operating System
Alpine Linux 3.18
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the supplied PDO example against PostgreSQL with PDO::ATTR_EMULATE_PREPARES enabled and disabled, focusing on bindValue() with PDO::PARAM_BOOL and a null value. Trace the PDO emulated-prepare path and compare both results; done when emulated prepares also return NULL and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, postgresql
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100