DDC-485: Doctrine\DBAL\Connection::_bindTypedValues() must implement interface Doctrine\DBAL\Driver\Statement #608

New Issue

admin · 2026-01-22T12:44:13+01:00

admin commented

2026-01-22 12:44:13 +01:00

Originally created by @doctrinebot on GitHub (Mar 30, 2010).

Jira issue originally created by user mridgway:

I haven't fully investigated this, but doing an update on trunk today I started receiving the following error message:

Catchable fatal error: Argument 1 passed to Doctrine\DBAL\Connection::_bindTypedValues() must implement interface Doctrine\DBAL\Driver\Statement, instance of PDOStatement given, called in ./library/Doctrine/DBAL/Connection.php on line 639 and defined in ./library/Doctrine/DBAL/Connection.php on line 869

This is occurring when a row is updated to point to the related field in another row (when both are persisted at the same time). It doesn't actually break the updates (with xdebug installed anyway).

It only appears to occur with a select few of my models that contain cascaded persists (and I'll be sure to attempt a test case for this for tomorrow). I haven't tested this fully but wanted to post this in case anyone has an idea of why this might be happening.

Originally created by @doctrinebot on GitHub (Mar 30, 2010). Jira issue originally created by user mridgway: I haven't fully investigated this, but doing an update on trunk today I started receiving the following error message: `Catchable fatal error: Argument 1 passed to Doctrine\DBAL\Connection::_bindTypedValues() must implement interface Doctrine\DBAL\Driver\Statement, instance of PDOStatement given, called in ./library/Doctrine/DBAL/Connection.php on line 639 and defined in ./library/Doctrine/DBAL/Connection.php on line 869` This is occurring when a row is updated to point to the related field in another row (when both are persisted at the same time). It doesn't actually break the updates (with xdebug installed anyway). It only appears to occur with a select few of my models that contain cascaded persists (and I'll be sure to attempt a test case for this for tomorrow). I haven't tested this fully but wanted to post this in case anyone has an idea of why this might be happening.

admin added the Bug label 2026-01-22 12:44:13 +01:00

admin closed this issue

2026-01-22 12:44:14 +01:00

admin commented

2026-01-22 12:44:16 +01:00

@doctrinebot commented on GitHub (Mar 31, 2010):

Comment created by romanb:

Hm, are you creating the PDO instance yourself (and passing it to Doctrine via the 'pdo' option)? That might be the reason.

@doctrinebot commented on GitHub (Mar 31, 2010): Comment created by romanb: Hm, are you creating the PDO instance yourself (and passing it to Doctrine via the 'pdo' option)? That might be the reason.

admin commented

2026-01-22 12:44:16 +01:00

@doctrinebot commented on GitHub (Mar 31, 2010):

Comment created by romanb:

I'm not sure whether we should just remove the typehint and use duck-typing there or whether we should enforce a better way.

@doctrinebot commented on GitHub (Mar 31, 2010): Comment created by romanb: I'm not sure whether we should just remove the typehint and use duck-typing there or whether we should enforce a better way.

admin commented

2026-01-22 12:44:18 +01:00

@doctrinebot commented on GitHub (Mar 31, 2010):

Comment created by mridgway:

Yes, we are passing a PDO instance to Doctrine.

@doctrinebot commented on GitHub (Mar 31, 2010): Comment created by mridgway: Yes, we are passing a PDO instance to Doctrine.

admin commented

2026-01-22 12:44:19 +01:00

@doctrinebot commented on GitHub (Mar 31, 2010):

Comment created by romanb:

Should be fixed now. The method in question now uses duck-typing.

@doctrinebot commented on GitHub (Mar 31, 2010): Comment created by romanb: Should be fixed now. The method in question now uses duck-typing.