On Mon, 22 May 2000, Perrin Harkins wrote:
On Mon, 22 May 2000 [EMAIL PROTECTED] wrote:
It seems the Apache::Session::DBI isn't actually changing anything
in the database, since next time I tie the session the only thing
it has is the _session_id I tied it with in the first place.
Keep
Am I correct in assuming that my tied session variable (using
Apache::Session::DBI), which I have stored away in a pnote,
is no longer tied when I try to retrieve it in a later
handler?
Is there a way to keep the same tied %session between handlers?
I remember someone talking about passing
At 09:03 22/05/2000 -0400, [EMAIL PROTECTED] wrote:
Am I correct in assuming that my tied session variable (using
Apache::Session::DBI), which I have stored away in a pnote,
is no longer tied when I try to retrieve it in a later
handler?
I routinely stuff my %session tied hash into a pnote, and
At a later hour on 22/05/2000, [EMAIL PROTECTED] wrote:
At 09:03 22/05/2000 -0400, [EMAIL PROTECTED] wrote:
Am I correct in assuming that my tied session variable (using
Apache::Session::DBI), which I have stored away in a pnote,
is no longer tied when I try to retrieve it in a later
handler?
I
On Mon, 22 May 2000 [EMAIL PROTECTED] wrote:
It seems the Apache::Session::DBI isn't actually changing anything
in the database, since next time I tie the session the only thing
it has is the _session_id I tied it with in the first place.
Keep in mind that Apache::Session only writes to the
At 19:10 22/05/2000 -0400, [EMAIL PROTECTED] wrote:
At a later hour on 22/05/2000, [EMAIL PROTECTED] wrote:
I routinely stuff my %session tied hash into a pnote, and it works fine.
All I do is something like $r-pnotes('session') = \%session;
Thank you, Robin.
You're welcome :)
That was exactly
