Re: [DataMapper] Re: Dates

2013-09-30 Thread Kilian Sprotte
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 DateTime property instead?


 On 09/29/2013 03:25 AM, kilian.spro...@gmail.com wrote:

 Hi,

 I am new to DataMapper, trying it out with sqlite3.

 I declared a property as

  property :created_at, Time, :default = lambda {|r,p| Time.now }

 What confuses me is that the created_at property ends up
 in the db as '2013-09-29T12:14:09.074859+02:00', but when
 I access it from ruby, I get a truncated Time object:
 2013-09-29 00:00:00 +0200

 Can someone explain? Is this a bug?

 See below for a list of installed gems.

 Best,
 Kilian

 dm-aggregates (1.2.0)
 dm-constraints (1.2.0)
 dm-core (1.2.1)
 dm-do-adapter (1.2.0)
 dm-migrations (1.2.0)
 dm-serializer (1.2.2)
 dm-sqlite-adapter (1.2.0)
 dm-timestamps (1.2.0)
 dm-transactions (1.2.0)
 dm-types (1.2.2)
 dm-validations (1.2.0)
 dm-sqlite-adapter (1.2.0)
 do_sqlite3 (0.10.13)
 sqlite3 (1.3.8)

 On Saturday, April 16, 2011 4:06:50 PM UTC+2, DAZ wrote:

 Hi,

 The docs say the following date types are available:

   DateTime, Date, Time

 I have always just used DateTime, but would actually like to work in
 seconds and therefore use a Time object.

 Is there any difference in the background in using Time as a type?

 e.g.:

   property :created_at,   Time, :default =  proc { |m,p| Time.now}

 cheers,

 DAZ

 --
 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 datamapper+unsubscr...@googlegroups.com.

 To post to this group, send email to datamapper@googlegroups.com.
 Visit this group at http://groups.google.com/group/datamapper.
 For more options, visit https://groups.google.com/groups/opt_out.



 --
 Blog: http://postmodern.github.com/
 GitHub: https://github.com/postmodern
 Twitter: @postmodern_mod3
 PGP: 0xB9515E77

 --
 You received this message because you are subscribed to a topic in the
Google Groups DataMapper group.
 To unsubscribe from this topic, visit
https://groups.google.com/d/topic/datamapper/d5cLJXAznuQ/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
datamapper+unsubscr...@googlegroups.com.
 To post to this group, send email to datamapper@googlegroups.com.
 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 datamapper+unsubscr...@googlegroups.com.
To post to this group, send email to datamapper@googlegroups.com.
Visit this group at http://groups.google.com/group/datamapper.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [DataMapper] Re: Dates

2013-09-30 Thread kilian . sprotte
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 datamapper+unsubscr...@googlegroups.com.
To post to this group, send email to datamapper@googlegroups.com.
Visit this group at http://groups.google.com/group/datamapper.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [DataMapper] Re: Dates

2013-09-30 Thread christian
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, kilian.spro...@gmail.com 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 datamapper+unsubscr...@googlegroups.com.
 To post to this group, send email to datamapper@googlegroups.com.
 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 datamapper+unsubscr...@googlegroups.com.
To post to this group, send email to datamapper@googlegroups.com.
Visit this group at http://groups.google.com/group/datamapper.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [DataMapper] Re: Dates

2013-09-30 Thread Kilian Sprotte
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 '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, kilian.spro...@gmail.com 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 datamapper+unsubscr...@googlegroups.com.
 To post to this group, send email to datamapper@googlegroups.com.
 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 datamapper+unsubscr...@googlegroups.com.
To post to this group, send email to datamapper@googlegroups.com.
Visit this group at http://groups.google.com/group/datamapper.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [DataMapper] Re: Dates

2011-04-16 Thread Martin Gamsjaeger
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
snusnu

On Sat, Apr 16, 2011 at 17:05, DAZ daz4...@gmail.com wrote:

 Thanks for the reply Michishige. I understand the differences between
 the 3 Ruby date types, but wondered what DM did behind the scenes with
 these ... are there any differences in how they are saved in the
 underlying DB?

 DAZ

 On Apr 16, 3:49 pm, Michishige Kaito chris.webs...@gmail.com wrote:
  On Sat, 16 Apr 2011, DAZ wrote:
   Hi,
 
   The docs say the following date types are available:
 
DateTime, Date, Time
 
   I have always just used DateTime, but would actually like to work in
   seconds and therefore use a Time object.
 
   Is there any difference in the background in using Time as a type?
 
   e.g.:
 
property :created_at,   Time, :default =  proc { |m,p| Time.now}
 
   cheers,
 
   DAZ
 
  The differences lie in the Ruby types you'll be working with, as the
 types
  correspond with Ruby date and time classes. I suggest you have a look at
  their documentation and judge by yourself.
 
  As far as I'm concerned, DateTime has support for timezones and some
 other
  fancy things, while both Date and Time are a little simpler. Depends on
  your needs. I usually just use Date or Time.

 --
 You received this message because you are subscribed to the Google Groups
 DataMapper group.
 To post to this group, send email to datamapper@googlegroups.com.
 To unsubscribe from this group, send email to
 datamapper+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/datamapper?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
DataMapper group.
To post to this group, send email to datamapper@googlegroups.com.
To unsubscribe from this group, send email to 
datamapper+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/datamapper?hl=en.