Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of iBiryukov:
...r unchanged DateTime objects
computeChangeSet method in unitOfWork compares original and new data using 'identical' (===) operator. This works well, except for DateTime objects.
Two different DateTime objects that contain the same data, should not trigger an unnecessary UPDATE query.
I made changes to account for this case.
Comment created by @doctrinebot:
A related Github Pull-Request [GH-814] was closed:
Issue was closed with resolution "Invalid"