FWIW, I've found this sort of stuff to be better done with CURRENT_TIMESTAMP than NOW() , or doing a "NOT NULL" constraint with no-default and passing in a time from the application.
On databases that support it, CURRENT_TIMESTAMP is locked to the transaction and/or statement while NOW() is evaluated in real-time. When you're doing some sort of create&modified date, there's an element of record keeping involved. By using NOW() instead of CURRENT_TIMESTMAP , you lose the ability to correlate any of the database updates in the same transaction/back together -- or to a specific web/application request. You could keep your pg logs for a long time and be willing to sort through them, but using CURRENT_TIMESTAMP gives fewer unique times. So so so much easier for auditing. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
