> 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?
>
> -- Travis
I already answered part of the part of the problem (with LastLogin).
Modified is more difficult. But the straightforward way is to set a
modified flag (the time) in every set method (I think maybe just setPerm in
TurbineUser, it may be more if you subclass it.) Then on a save call, the
correct date will get written. At present even if the Modified column is
updated automatically by MySQL, it will get overwritten with the value
stored in TurbineUser when it is unBound.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
