------=_Part_4406_7148508.1146155653017
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

>
>
> you could also just have apache::session update that column as well
> on the data store by overrideing the store mechanism
>



If you're using MySQL 4.1 or above for your db store, you can also use a
timestamp column like:

ts timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP

MySQL should keep the timestamp current for every update for this column. O=
f
course the earlier comment about the extra work for the db still applies.
Leaving off the "on update CURRENT_TIMESTAMP" part and overriding the updat=
e
method would save you the extra update per update. But if your db is pretty
unloaded, this is certainly the easiest way to go.

------=_Part_4406_7148508.1146155653017
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
you coul=
d also just have apache::session update that column as well
on the data =
store by overrideing the store mechanism



If you're using MySQL 4.1 or above for your =
db store, you can also use a timestamp column like:

ts timestamp NOT=
NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP

MySQL sh=
ould keep the timestamp current for every update for this column. Of course=
the earlier comment about the extra work for the db still applies. Leaving=
off the "on update CURRENT_TIMESTAMP" part and overriding the up=
date method would save you the extra update per update. But if your db is p=
retty unloaded, this is certainly the easiest way to go.



------=_Part_4406_7148508.1146155653017--