#6021: Wrong timestamp saving for automatic fields "created" and "modified"
-----------------------------------------+----------------------------------
Reporter: bugmenot | Owner:
Type: Test Case | Status: new
Priority: Medium | Milestone: 1.2.x.x
Component: General | Version: 1.2 Final
Severity: Normal | Resolution:
Keywords: mysql, CURRENT_TIMESTAMP | Php_version: PHP 5
Cake_version: 1.2.1.8004 |
-----------------------------------------+----------------------------------
Comment (by mulleto):
I stumbled across this issue today, too, and since changing from timestamp
to datetime is not an option for me, I took a look at what happens. If I
see right, the quoting done by the value() method in your Dbo_(dbtype)
does not have a handling for timestamp columns. Since the only issue is
not to have CURRENT_TIMESTAMP as default value being quoted, the simple
patch that I have attached would solve this. The Patch I provide is for
dbo_mysqli, but as far as I saw, most other dbos would work pretty much
the same.
--
Ticket URL: <https://trac.cakephp.org/ticket/6021#comment:6>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC.
Our primary goal is to provide a structured framework that enables PHP users at
all levels to rapidly develop robust web applications, without any loss to
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---
