On Mon, 29 Apr 2002, F. Xavier Noria wrote:
3. Could one set up things in a way that allows the database to see
the timestamps and program a trigger to delete old sessions? Or
is there a standard idiom for doing this in a different way?
thats what i usually do ...
If I understand it correctly, Apache::Session::Oracle uses a table
called sessions with at least two columns, one called id, of type
varchar2(32), and another called a_session, of type long.
Say I want to store a pair of things in sessions: a reference to an
object of type User (which includes
If I understand it correctly, Apache::Session::Oracle uses a table
called sessions with at least two columns, one called id, of type
varchar2(32), and another called a_session, of type long.
Say I want to store a pair of things in sessions: a reference to an
object of type User (which includes
If I understand it correctly, Apache::Session::Oracle uses a table
called sessions with at least two columns, one called id, of type
varchar2(32), and another called a_session, of type long.
Say I want to store a pair of things in sessions: a reference to an
object of type User (which includes
On Mon, 29 Apr 2002 01:11:59 +0200
F.Xavier Noria [EMAIL PROTECTED] wrote:
: If I understand it correctly, Apache::Session::Oracle uses a table
: called sessions with at least two columns, one called id, of type
: varchar2(32), and another called a_session, of type long.
I am sorry this
