>
> But another thing re sessions. I'm thinking about adding an "updated"
column
> and a trigger or something to be able to clean out old unused sessions.
>
> Or does Apache::Session(X) magically keep track of them?
>
Not yet, also I would like to see the Apache::SessionX does keep track of
updat
At Sat, 28 Sep 2002 12:32:37 +0200, Kaare Rasmussen wrote:
> But another thing re sessions. I'm thinking about adding an "updated" column
> and a trigger or something to be able to clean out old unused sessions.
>
> Or does Apache::Session(X) magically keep track of them?
no, and its actually a
> note that the latest version or two of DBD::Pg actually reports
> correct SQL types to DBI (which is probably why my DBIx::Recordset
> tests are failing now) and correctly escapes the binary BYTEA type.
OK, so I will try a bytea column with Storable. I don't think there will be a
big performan
At Thu, 26 Sep 2002 16:15:10 +0200, Kaare Rasmussen wrote:
> Thanks. I got it to work with
> Postgres Semaphore Base64
that will work, but you should be using "Postgres Null Base64"
> Not sure what is the best for serialization. Bas64, Dumper, ...??
> I haven't been able to find any discussion
At Sat, 28 Sep 2002 05:27:32 +0200, Gerald Richter wrote:
> > Not sure what is the best for serialization. Bas64, Dumper, ...??
> > I haven't been able to find any discussion about pro / con for this.
>
> As far as I know you should use Base64 for Postgres
note that the latest version or two of
>
> Not sure what is the best for serialization. Bas64, Dumper, ...??
> I haven't been able to find any discussion about pro / con for this.
>
As far as I know you should use Base64 for Postgres
Gerald
-
Gerald Richterecos elect
> in there somewhere will be the actual SQL statement being used, which
> should give some clues as to whats going wrong.
Thanks. I got it to work with
Postgres Semaphore Base64
Not sure what is the best for serialization. Bas64, Dumper, ...??
I haven't been able to find any discussion about p
> I'm trying to set up session support for Embperl.
>
> I'd like to use Postgres, so my application can scale better. But it seems
> that it uses semaphores for locking, and that the semaphores is placed on
> Apache's side. Wouldn't this prevent me from usin
At Tue, 24 Sep 2002 07:44:29 GMT, Kaare Rasmussen wrote:
> I'm trying to set up session support for Embperl.
> I'd like to use Postgres, so my application can scale better. But it seems
> that it uses semaphores for locking, and that the semaphores is placed on
> Apache
> Yes, but you don't need any locking for Postgres. Use the Null locker,
> Postgres itself takes care for data integrity. Then you can use it across
> multiple Apaches.
Thanks. I will try that out.
> Which parameters do give to Apache::SessionX Makefile.PL ?
I found an old message about the sa
I'm trying to set up session support for Embperl.
I'd like to use Postgres, so my application can scale better. But it seems
that it uses semaphores for locking, and that the semaphores is placed on
Apache's side. Wouldn't this prevent me from using two or more Apache
ser
11 matches
Mail list logo
