Something I use (and I know a lot of other people used) in their tables are a "date_created" and "date_modified" field. However, the date is always handled at the application level which doesn't seem like the best way to handle it.
Is there a generic way to handle this in Sequel? I'm not an SQL guru by any stretch, but it seems to me this is something that would have to go into a migration and not into model code. As an extra thought, I'll be importing some old data from a MySQL database and would like to preserve those dates. It seems that setting a default that was dynamic would handle the the date_created. The date_modified, however would require... a trigger? Yeah. Not a guru. -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. 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.
