No, in fact in PHP5 php now purposely resets the connection between pages.
You'd have to write some kind of pooling solution to get that kind of
behaviour. I don't know of anyone working on pooling in PHP.
On Fri, 31 Oct 2003, Stephen wrote:
> Any idea how the prepared query can be made to save across PHP invocations?
> How about using pg_pconnect (persistent connection), will it stay prepared
> when PHP comes again and reuse the connection?
> ""scott.marlowe"" <scott(dot)marlowe(at)ihs(dot)com> wrote in message
> > On Fri, 24 Oct 2003, Martin Marques wrote:
> > > El Vie 24 Oct 2003 15:02, Robby Russell escribió:
> > > > Stephen wrote:
> > > > > Hi,
> > > > >
> > > > > Does anyone know if PHP supports prepared queries for PostgreSQL
> 7.3.x ?
> > > If
> > > > > not, when will prepared queries be supported?
> > > > >
> > > > > Thanks, Stephen
> > > > >
> > > >
> > > > You might want to look at PEAR db. I think it comes with php standard
> > > > now... so pear.php.net.
> > >
> > > Those are not prepared queries (at least in the sence of prepare ->
> > > For prepared queries you have to know how to talk to libpq, and that's
> > > something that is done from the pgsql ext.
> > This hunk of code works fine on my php 4.3.2 / postgresql 7.3.4 box:
> > <?php
> > $conn = pg_connect("dbname=marl8412 user=marl8412");
> > $a = pg_query($conn,"prepare test (int4) as select * from accounts where
> > aid= $1");
> > $res = pg_query($conn,"execute test (45)");
> > $row = pg_fetch_row($res);
> > print implode(" ",array_values($row))."<BR>";
> > ?>
> > so yes, you can use a prepared queries in PHP. But, they won't live
> > across connections I don't think. Or at least I'm pretty sure you can't
> > count on them living from one page to the next. but if you're gonna have
> > a page where you run the same select with different select parameters over
> > and over it might be a win.
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: the planner will ignore your desire to choose an index scan if your
> > joining column's datatypes do not match
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
In response to
pgsql-php by date
|Next:||From: scott.marlowe||Date: 2003-11-05 15:38:57|
|Subject: Re: Support for prepared queries|
|Previous:||From: Robert Treat||Date: 2003-11-04 19:00:24|
|Subject: Re: Dead sequence|