Return-Path: 
 <modperl-return-51153-apmail-perl-modperl-archive=perl.apache.org@perl.apache.org>
Delivered-To: apmail-perl-modperl-archive@www.apache.org
Received: (qmail 57601 invoked from network); 27 Apr 2006 16:34:53 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 27 Apr 2006 16:34:53 -0000
Received: (qmail 18909 invoked by uid 500); 27 Apr 2006 16:34:36 -0000
Delivered-To: apmail-perl-modperl-archive@perl.apache.org
Received: (qmail 18892 invoked by uid 500); 27 Apr 2006 16:34:36 -0000
Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:modperl-help@perl.apache.org>
list-unsubscribe: <mailto:modperl-unsubscribe@perl.apache.org>
List-Post: <mailto:modperl@perl.apache.org>
List-Id: <modperl.perl.apache.org>
Delivered-To: mailing list modperl@perl.apache.org
Received: (qmail 18881 invoked by uid 99); 27 Apr 2006 16:34:36 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Apr 2006 09:34:36 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of moseleymark@gmail.com designates
 66.249.82.192 as permitted sender)
Received: from [66.249.82.192] (HELO xproxy.gmail.com) (66.249.82.192)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Apr 2006 09:34:35 -0700
Received: by xproxy.gmail.com with SMTP id s11so1350066wxc
        for <modperl@perl.apache.org>; Thu, 27 Apr 2006 09:34:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=jtb8XfZ57dESgOKHfMBwty4y0hWgewG+dDvY5bDbNZ6btNIhXBC7qlmMbD2ydobcn1VtCr/fDUrfTX15oceCzDs6TUnASPRol9Y0SS2HY+OHNUV4z7ftEBHHDE9UTKs5rPeJe5PSoeCMTChIk+bqatHIvfftyHw5KapePCv65MU=
Received: by 10.70.122.19 with SMTP id u19mr111320wxc;
        Thu, 27 Apr 2006 09:34:13 -0700 (PDT)
Received: by 10.70.28.13 with HTTP; Thu, 27 Apr 2006 09:34:13 -0700 (PDT)
Message-ID: <294d5daa0604270934q4be5a9d6t9f03a2f6766151c6@mail.gmail.com>
Date: Thu, 27 Apr 2006 09:34:13 -0700
From: "Mark Moseley" <moseleymark@gmail.com>
To: "Mod_Perl Mailing List" <modperl@perl.apache.org>
Subject: Re: Apache::Session: can I have a "date" in session
In-Reply-To: <C9A475BE-C62C-4C81-AF49-B68D85C2B72A@2xlp.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4406_7148508.1146155653017"
References: <20060427152050.GA3339@manifold.algebra.com>
	 <fd8e28ef0604270838l52933c36k4d12d4ac4dc1ee5@mail.gmail.com>
	 <C9A475BE-C62C-4C81-AF49-B68D85C2B72A@2xlp.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

------=_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

<div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(=
204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>you coul=
d also just have apache::session update that column as well<br>on the data =
store by overrideing the store mechanism
<br></blockquote></div><br><br>If you're using MySQL 4.1 or above for your =
db store, you can also use a timestamp column like:<br><br>ts timestamp NOT=
 NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP<br><br>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 &quot;on update CURRENT_TIMESTAMP&quot; 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.
<br>

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