Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of tomsowerby:
...te-key id attributes.
Bug discovered when using a table with 2 columns, both being used as a composite primary key.
Php Datetime class was extended to implement a **toString function (as described here http://stackoverflow.com/a/15085566), but this was not being called because doctrine was not recognising the entity as having a composite primary key (due to the non-datetime user key being joined via foreign key (which may in itself be a bug)).
When adding an extra empty text field as part of the composite key, everything worked, it's just because the only non-joined-column was an object, and it managed to avoid the (implode) code that would have cast it as a string.
This change casts the object, in this case a custom datetime, to a string, if it is not part of a composite key.
Comment created by @doctrinebot:
A related Github Pull-Request [GH-750] was closed:
A related Github Pull-Request [GH-750] was reopened:
Issue was closed with resolution "Invalid"