#1543: timestampable doesn't update the 'updated_at' columns anymore
-----------------------------------+----------------------------------------
Reporter: klemens_u | Owner: jwage
Type: defect | Status: new
Priority: major | Milestone:
Component: Timestampable | Version: 1.0.2
Keywords: | Has_test: 0
Mystatus: Pending Core Response | Has_patch: 0
-----------------------------------+----------------------------------------
The reason for this is the fix from ticket #1473 resulting in change
r4987.
The motivation was to allow manual overwriting of the timestamps values.
But the implemented solution doesn't work as desired. It breaks the
behaviour for normal updates -> the 'updated_at' columns aren't updated at
all anymore.
At the moment the listener just looks if the created_at or update_at field
is set at all in the object. And of course it is always set after the
first save.
Solution: The listener has to be able to find out if the created_at or
updated_at columns have been set/changed in comparison with the values in
the db. Only in this case the normal timestampable behavior may be
overwritten.
Sorry for my bad explanation, I hope you get it ;-)
@see:
http://groups.google.com/group/doctrine-
user/browse_thread/thread/7b8ee0b85b80315e/d7970709a3902315?lnk=gst&q=doctrine+timestampable#
--
Ticket URL: <http://trac.doctrine-project.org/ticket/1543>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
