Jeremy-
It is a timezone issue. The string from the column has already been adjusted for timezone. Then when I make a DateTime using #strptime it creates it with a time zone +0. How would I deal with this? To get the timezone adjustment in the column value string, I have to cast is as CAST(<column> AS TIMESTAMP WITH TIME ZONE). Or do I use ruby to supply that to strptime? -GregD ----- Original Message ----- From: "Jeremy Evans" <[email protected]> To: [email protected] Sent: Friday, August 30, 2013 11:58:36 AM Subject: Re: SqlAnywhere Adapter Timestamp problems On Friday, August 30, 2013 8:38:22 AM UTC-7, GregD wrote: Testing on a localhost. Try the following: p Time.now p DB.get(Sequel::CURRENT_TIMESTAMP) If the two outputs are not close to each other, that's where the problem is. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk . For more options, visit https://groups.google.com/groups/opt_out . -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
