Tickets :: Comment on [#14803] Horde_Rdo_Mapper sets created_at, forgets updated

Search Results: 10 of 17 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: .__.. .._..__..___ [__]\|_/ \| \| \|[__ \| \|\| \_\|_\|__\\|
Comment	> I am using an RdoMapper on a table created with $t->timestamps() on a > Horde_Db_Migration_Base object. Columns created_at and updated_at are > created right away in the backend. > > According to Mapper.php (line 342 ff.), both fields should be set to > the current timestamp on create(). According to lines 388 ff. > updated_at should be set on update(). While created_at functions all > right, updated_at remains set to 0000-00-00 00:00:00. No change on > creation or update.
Attachment
Watch this ticket