> I worked around the problem by changing the name but in my opinion > this is not how it should work.
Ok, so you are only concerned about the data type. As I suggested you could get around this issue using callbacks: beforeSave() to change the Unix timestamp to a Cake friendly date/time on save, and back again with afterFind() when retrieving. The problem here isn't so much inflexibility (in my opinion) as a trade off. Cake could be made infinitely flexible, but it would then defeat the basic idea of the framework (i.e. rapid development). As it stands, your problem can likely be solved with a minimum of fuss by Cake's existing features. Regards, Langdon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
