I think this is symfony thing, but you can always override this and still use the column name updated_at.
On Feb 2, 2008 1:43 PM, James <[EMAIL PROTECTED]> wrote: > > When I create my schema I use create_at: and updated_at: created at > is datetime, and that makes sense, but why is updated_at classified > as datetime and not a true "timestamp"? I can see if symfony/propel > wants to update it with it's time, but there are times I see I will do > things manually and because it's not a timestamp type in mysql then it > doesn't record anything I do outside of symfony into the timestamp. > This is kind of annoying. Ideas? > > James > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
