On Mon, 29 May 2000, Michael Blakeley wrote:
> Patch for Apache::Session::Store::Postgres, from
> Apache-Session-1.51.tar.gz, to resolve problems with
>
> >prepare_cached(SELECT a_session FROM sessions WHERE id = ? FOR
> >UPDATE) statement handle DBI::st=HASH(0x369a2c) is still active
>
> after a transient error. The solution is to call sth->finish()
> whether the SELECT was successful or not.
>
> diff Store/Postgres.pm.orig Store/Postgres.pm
> 78a79,81
> > # success or failure, don't leave FOR UPDATE lying around
> > $self->{materialize_sth}->finish;
> >
> 83,84d85
> < $self->{materialize_sth}->finish;
> <
Hrmm, I'm not really an expert here. If I do a SELECT ... FOR UPDATE on a
row that doesn't exist, shouldn't that just do nothing?
To squash this warning, we could just as easily use the allow_active flag
in the prepare method.
-jwb
