[EMAIL PROTECTED] wrote:
This seems to be a problem with PHP, or at least my set up.
I'm writing pages in basically the same way. Each page has an include
at the top that gets you a database session. The function, either
pg_connect() or mysql_connect(), is supposed to either create a new
connection, or return your existing one.
So after I have a connection, I can navigate to other pages, reload or
post to the current one, trigger the x_connect(), and get the session
I created earlier.
In my Mysql site, if I create temporary tables, I still have access to
them after I have traversed a mysql_connect. So it looks like PHP is
giving me the connection I had when I created the temp tables.
However, with this new Postgres site, I don't have access to my temp
tables after I've traversed another pg_connect. So PHP is either
creating a new connection, or giving me another session, not the one
which I created my tables in.
MySQL reuses old connections within the same script. PostgreSQL's php
extension does not, it starts a new connection each time.
MySQL's behaviour is surprising, PostgreSQL's behaviour is what you'd
expect. Which is typical of both dbs.
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
