sqlite3 is anyways different since it just stores a 'string' as date or datetime the latter including millis and nanos. but any(?) other database just has a precision up to seconds. I personaly use Date and DateTime with UTC timezone when storing them in a database.
just my thoughts . . . -christian On Mon, Sep 30, 2013 at 2:58 PM, <[email protected]> wrote: > Hi, > > the concern of a truncated Time does not occur with postgresql, only with > sqlite3 (I have only tried the 2 so far). > > Best, > Kilian > > -- > You received this message because you are subscribed to the Google Groups > "DataMapper" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/datamapper. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "DataMapper" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/datamapper. For more options, visit https://groups.google.com/groups/opt_out.
