Travis Low wrote:
>
> Has no one seen this problem, or is it a dumb question? I worked
> around it by maintaining login/create/modify time information in a
> separate table, and updating myself upon login or logout. But I'm not
> thrilled about it.
>
> Incidentally, mySQL has a "feature" that the first TIMESTAMP column in
> any record is automagically updated with the current time whenever
> that record is modified in any way. Is that consistent with the
> intent of the Visitor.MODIFIED column?
I don't know the answer, but regardless, I vote for documenting this
fact in the MySQL schema.
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
