>
> i get nervous about automatically committing on DESTROY.
>
That's reasonable
> I changed Store::Postgres to rollback if Transaction=>1 is given, and
> they did not explicitly call insert(), update() or remove() (which do
> a commit of their own).
>
> The "official" Store::Postgres doesn't use the Transaction option, so
> i hoped this wouldn't affect existing users.
>
>
> Theoretically, you could give neither Transaction nor Commit, and you
> would have an outstanding transaction, that you need to commit (or
> rollback) yourself (outside Apache::Session). as far as i could tell,
> this was the expected behaviour when Commit wasn't given. This, and
> not affecting existing users, was the reason i didn't just use "if
!Commit".
>
I would more like the "if !Commit" solution, because if you like
Apache::Session todo the commit for, then I would expect that it also does
the rollback, in case something went wrong.
>
> gerald, if the Apache::Session author has disappeared, i'm tempted to
> just take/fork it and start "fixing" it.
>
No, he isn't disapeared (his last post on the mod_perl list was yesterday),
he is simply very busy and so he isn't very responsible. Also he didn't like
the idea to build too much features into Apache::Session itself, he more
like the idea that other people derive from Apache::Session to implement
thier own features. That's the reason why I created HTML::Embperl::Session,
as a module that inherits from Apache::Session.
At the moment I started to convert HTML::Embperl::Session to
Apache::SessionX, which get extented features that I need for Embperl. I add
new features to have a better session handling in Embperl itself and
Apache::SessionX has the ability to overload the classes of Apache::Session
so we can quickly fix them. So I will build your rollback into
Apache::SessionX. Additionaly Apache::SessionX, will create a new storages
object (not the APache::SessionX object itself) for every request, so we are
sure all data is written, commited and unlock without the need of "close"
hack. As last point (for the first release), Apache::SessionX should make
configuration of Session much more easier (which is often a problem, as you
can see by the mails on the list)
I think I will have a test version ready during next week and I send you a
copy, so you can test it against Postgres in your environment.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
