BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: https://bugs.horde.org/ticket/14803
------------------------------------------------------------------------------
Ticket | 14803
Erstellt Von | [email protected]
Zusammenfassung | Horde_Rdo_Mapper sets created_at, forgets updated_at
Warteschlange | Horde Framework Packages
Typ | Bug
Status | Unconfirmed
Priorität | 1. Low
Milestone |
Patch |
Zuständige |
------------------------------------------------------------------------------
[email protected] (2018-04-03 22:42) hat geschrieben:
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.
--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.