I'll have to read up on triggers then. I'm guessing that this will require literal SQL in my migrations.
On Sep 23, 6:31 am, byrnejb <[email protected]> wrote: > On Sep 23, 2:06 am, cult hero <[email protected]> wrote: > > > It looks like this is done at the application level. I could be wrong. > > (Am I?) If I am, it is what I'm looking for. If not, it's not quite > > there because the time is being set by the application and not by the > > database. > > The Web 2.0 idiom is that everything is done in the application and > that the DBMS is is simply a bit bucket. To have your DBMS handle so- > called 'magic columns' requires that you write a trigger for each > table in your database that requires timestamps. > > This is in fact what I do with my PostgreSQL databases since, in my > opinion, allowing an external source set DBMS activity timestamps is a > gross violation of any prudent auditing process. -- 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.
