Hi! On 01/08/2008 10:43 AM Thomas Koch wrote:
> I know you'll hate me, but I've got another 2cents. ;-) > > I set up a db with a timestamp column (since DatabaseSchema supports it) and > wanted to use it in PO with the new date converter. Unfortunately for me the > converter accepts only time values as integer timestamps, but MySQL returns > strings like '2008-01-08 10:14:08'. > > I'd still love to use native timestamp columns because they are much nicer to > read, when you access the db directly. My suggestion is to have two different > datetime converters: one to int and one to timestamp. > > I could also write this additional converter, if you're allright with the > idea. Only that DatabaseSchema supports the "timestamp" column does not mean that we support in PersistentObject. Values of this datatype are not easily portable and it is generally discouraged to make use of it when writing portable applications. Therefore: Please use integer fields to store your date/time data. Regards, Toby -- Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer [EMAIL PROTECTED] | eZ Systems AS | ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
