Hi,
thanks for replying! I will try DateTime. I do not really understand the
solution, though. If I had tried to use Date, ok, but shouldn't Time work
equally in this respect to DateTime?
Best
Kilian
On Sep 30, 2013 12:33 AM, postmodern postmodern.m...@gmail.com wrote:
I think you want a
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
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 . . .
Hi! Still strange with sqlite3 to see the string
'2013-09-29T12:14:09.074859+
02:00' in the db and to get a Time 2013-09-29 00:00:00 +0200. Should this
be reported as a bug?
On Mon, Sep 30, 2013 at 4:12 PM, christian m.krist...@web.de wrote:
sqlite3 is anyways different since it just stores a
DAZ,
Have a look at:
https://github.com/datamapper/dm-migrations/blob/master/lib/dm-migrations/adapters/dm-do-adapter.rb#L284-286
Note that this is the base behavior. Other adapters in that folder may or
may not overwrite these defaults, based on the respective datastore's
abilities.
cheers
