On 6/9/05, [EMAIL PROTECTED] wrote: > > Okay, so I understand the idea about one field being the "creation" time, and > the other being the "last modified" time (which a particularly pedantic > application might regard as being one-and-the-same, at time of > first-creation) and so I see you might want to _store_ that fact in both > fields at time of creation: but even so, there is a fundamental difference of > type between the two fields, that remains, that is much more important than > the fact you can declare them both as DEFAULT NOW()... "Time of creation" > must never change; or it's existence is useless. "Time of modification" must > _always_ change; or it's existence is useles.
Not necessarily. Sometimes you want to differentiate between 'Last user modification' and 'Last process modification'. One way to handle that is in a trigger based upon the group membership of the user making the change. > That kind of logic can only really be enforced by external business rules > built into the code, anyway, can't it? No. Jochem -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
