Comments on: Rails, PostgreSQL and Time http://marcus.ahnve.net/2007/05/09/rails-postgresql-and-time/ A northern, icebears-on-the-streets, view on programming, music etc. from Marcus Ahnve Thu, 20 Nov 2008 21:39:46 +0000 http://wordpress.org/?v=2.6 By: Marcus http://marcus.ahnve.net/2007/05/09/rails-postgresql-and-time/#comment-20057 Marcus Mon, 11 Jun 2007 06:18:38 +0000 http://marcus.ahnve.net/2007/05/09/rails-postgresql-and-time/#comment-20057 <p>Interesting bug, I hadn't thought of that.</p> <p>I try to stay clear of MySQL, there are too many stories of data corruptiion around.</p> Interesting bug, I hadn’t thought of that.

I try to stay clear of MySQL, there are too many stories of data corruptiion around.

]]> By: Fotos Georgiadis http://marcus.ahnve.net/2007/05/09/rails-postgresql-and-time/#comment-19958 Fotos Georgiadis Sat, 09 Jun 2007 00:24:58 +0000 http://marcus.ahnve.net/2007/05/09/rails-postgresql-and-time/#comment-19958 <p>No you are not...</p> <p>Just got bitten by this. This is how: I have a model with attributes time<em>start and time</em>end of type :time (time without timezone in PostgreSQL) and one validation that (yes you guessed it) checks whether time<em>start > h = WorkingHour.find(1) => #"1", "id"=>"1", "time</em>end"=>"15:00:00", "time<em>start"=>"08:00:00", "photographer</em>id"=>"1"}> >> h.valid? => true >> h.time<em>end => Sat Jan 01 15:00:00 +0200 2000 >> h.time</em>start => Sat Jan 01 08:00:00 +0200 2000 >> h.time<em>start = Time.now => Sat Jun 09 03:17:50 +0300 2007 >> h.time</em>end<br /> => Sat Jan 01 15:00:00 +0200 2000 >> h.valid? => false >> h.errors.full_messages => ["Starting time must be before ending time"]</p> <p>This is a bug that needs fixing! What's the behaviour in MySQL btw?</p> No you are not…

Just got bitten by this. This is how: I have a model with attributes timestart and timeend of type :time (time without timezone in PostgreSQL) and one validation that (yes you guessed it) checks whether timestart > h = WorkingHour.find(1) => #”1″, “id”=>”1″, “timeend”=>”15:00:00″, “timestart”=>”08:00:00″, “photographerid”=>”1″}> >> h.valid? => true >> h.timeend => Sat Jan 01 15:00:00 +0200 2000 >> h.timestart => Sat Jan 01 08:00:00 +0200 2000 >> h.timestart = Time.now => Sat Jun 09 03:17:50 +0300 2007 >> h.timeend
=> Sat Jan 01 15:00:00 +0200 2000 >> h.valid? => false >> h.errors.full_messages => ["Starting time must be before ending time"]

This is a bug that needs fixing! What’s the behaviour in MySQL btw?

]]>