SQLFilter gives an unclear error when using non-Stringable parameters #7439

New Issue

admin · 2026-01-22T15:51:41+01:00

admin commented

2026-01-22 15:51:41 +01:00

Originally created by @7-zete-7 on GitHub (Nov 6, 2024).

Bug Report

Q	A
Version	~3

Summary

In ORM 2, parameters were converted according to the DBAL types passed with the parameters. In ORM 3 (after https://github.com/doctrine/orm/pull/9727), parameters began to be explicitly converted to a string.

Current behavior

Error while explicitly converting to string.

Expected behavior

Converting specified parameters according to the passed types.

Reproducer: https://github.com/7-zete-7/doctrine-orm-reproducer-1

[critical] Uncaught PHP Exception Error: "Object of class Symfony\Component\Clock\DatePoint could not be converted to string" at SQLFilter.php line 109

Originally created by @7-zete-7 on GitHub (Nov 6, 2024). ### Bug Report  | Q | A |-------------------------------------------- | ------ | Version | ~3 #### Summary In ORM 2, parameters were converted according to the DBAL types passed with the parameters. In ORM 3 (after https://github.com/doctrine/orm/pull/9727), parameters began to be explicitly converted to a string. #### Current behavior Error while explicitly converting to string. #### Expected behavior Converting specified parameters according to the passed types. Reproducer: https://github.com/7-zete-7/doctrine-orm-reproducer-1 ``` [critical] Uncaught PHP Exception Error: "Object of class Symfony\Component\Clock\DatePoint could not be converted to string" at SQLFilter.php line 109 ```

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#7439

SQLFilter gives an unclear error when using non-Stringable parameters #7439

Bug Report

Summary

Current behavior

Expected behavior

`SQLFilter` gives an unclear error when using non-`Stringable` parameters #7439