Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
From: Malcolm J Harwood <mjhlist-modperl@liminalflux.net>
To: modperl@perl.apache.org
Subject: Re: apache::session not writing to db
Date: Sun, 18 Dec 2005 15:01:29 -0500
User-Agent: KMail/1.8.2
References: <20051218193113.96071.qmail@web60422.mail.yahoo.com>
In-Reply-To: <20051218193113.96071.qmail@web60422.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200512181501.29997.mjhlist-modperl@liminalflux.net>

On Sunday 18 December 2005 02:31 pm, Michael Greenish wrote:

> Note that I set 'stuff' immediately after the session
> is created.  I would expect at this point that the
> database be updated.

That's incorrect. The database is only updated when the session is untied 
(usually on going out of scope).

> The session is inserted into the sessions table, but
> the a_session is never updated.  I tried using the
> tied( %session )->make_modified, and I tried untie(
> %session ) when I am done with the request, but none
> of those seem to cause anything to be written in the
> database.

untie %session should work. What happens if you do that in your constructor 
after:

>	$session{'stuff'} = 'is this in the database?';

If that works, you've got a problem in your code somewhere. If it doesn't, the 
it could be a db permissions issue or something. Do you get any errors in 
your logs?


-- 
If you want to kiss the sky 
Better learn how to kneel
- 'Mysterious Ways' U2