On Friday, August 3, 2012 9:43:28 AM UTC-7, blambeau wrote: > > Thanks for your answer. > > Actually, the reason I'm facing this issue is that I work with sqlite for > my tests, but the sqlite database is built with a schema dump from a legacy > database in postgresql. > > The fact is that I'm forced to use "sequel -D" for now because the current > timestamp default value (:default=>"now()".lit)is not inferred by "sequel > -d". >
I always recommend testing using the same database type you are using in production, as it avoids a lot of problems. Still, the root cause of your problem is that Sequel doesn't translate 'now()' to a generic ruby value. It would be helpful if that were translated to Sequel::CURRENT_TIMESTAMP when -d is used. I've added that to my todo list, it should hopefully make it into the next version. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/IfSQLuslmcgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
