I worked around the problem by changing the name but in my opinion this is not how it should work.
Currently I am developing a system for project management in cake and we need the unix timestamp for interchanging purposes. It is the format which is understood by all of our (non-cake-)systems without conversation. So it is the most secure and the most simple solution and therefore obligatory at our company. So I cannot/should not change the datatype. This leaves only the option of changing name. But: "created" is some kind of unwritten rule for naming a field with the timestamp of the creation time in it. Of course I can name the field "registered" in the user-table, "added" in the products-table and so on but "created" would be the name one would normally choose. Furthermore I have to change the views in most of the cases because e.g. the xml-export has to have it called "created" - again for interchanging purposes. I do not know if I should open a ticket for this because I think it is a feature not a bug but when it comes to integrate cake in large environments this is an obstacle that is not necessary in my opinion. The simpliest would be to check the datatype in the db and it is is not datetime it is treated like any normal field is. I tried to do it myself but maybe I am simply too stupid and could not find a way to achiev it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
