Jira issue originally created by user @beberlei:
This issue is created automatically through a Github pull request on behalf of Romain-Geissler:
DBAL allows you to define custom field types for your entities, and those are seamlessly converted from PHP to SQL value. However, you can't those custom types as parameters without type hinting it :
->where('e.customField = :customFieldValue')
//this third argument is for now compulsory
In my case, $customFieldValue is an object that won't work well if converted with the default string type. I added a new DBAL interface (see doctrine/dbal#193 ) and tweaked the parameter type inference so that custom values can advertise their DBAL type.
There is currently no way to dynamically override the parameter type inference logic, this is one design that allows it in some cases.
Comment created by @beberlei:
A related Github Pull-Request [GH-432] was closed
Comment created by @doctrinebot:
A related Github Pull-Request [GH-432] was closed: