On Mar 13 Nov 2001 17:36, you wrote:
> I was wondering if it were possible to store a database connection in a
> session variable.
No! Because the persistent connection gets opened with one child, and when
you go for the next page you have very high probabilities (unless you have a
very poor http configuration) of caching a new child, and not the old one.
The problem comes here, just because the pconnect was done against the old
child, and the new one doesn't know a thing about the pconnect you did
before, so you'll allways (or almost always) an error of "wrong connection
id".
Hope I was clear.
> I have tried these 2 methods:
>
> $conn = pg_pconnect("server", "5432", "db");
> session_start();
> session_register('conn');
>
> $conn = pg_pconnect("server", "5432", "db");
> session_id($conn);
> session_start();
>
> both of them register a session with the value of "Resource id #1" but
> don't act as a db connection. I am just trying to clean up some code so I
> don't have to do a new database connection on every page that I create.
>
> Then if you are able to do this, where would you close the connection?
>
> I guess in ASP, it is possible to store db connections in a session
> variable. I have never done it there either but someone told me that you
> can.
>
> Tim.
>
> Timothy P. Maguire
> Web Developer II
> Harte-Hanks
> 978 436 3325
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-----------------------------------------------------------------
Martín Marqués | mmarques@unl.edu.ar
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------
