On Wednesday, September 7, 2016 at 1:29:43 PM UTC-5, Jeremy Evans wrote: > > In general, I recommend using CURRENT_TIMESTAMP in queries instead of > literal timestamp values representing the current timestamp (which is what > you get if you use Time.now.utc). I'm guessing you are using the > timestamps plugin. I would also recommend using the > current_datetime_timestamp extension on the database, and then using > Person.dataset.current_datetime instead of Time.now. Additionally, you may > want to use the update_refresh plugin to ensure the model's column values > are updated to the database's values after update. > > Also, if you are using PostgreSQL, look at having timestamps implemented > using sequel_postgresql_triggers instead of trying to use a model plugin. > > Thanks, > Jeremy >
This all sounds great -- thank you for the advice! - Trevor -- 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 sequel-talk+unsubscr...@googlegroups.com. To post to this group, send email to sequel-talk@googlegroups.com. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
