Skip site navigation (1) Skip section navigation (2)

scope of connection id (handler)

From: "G(dot) J(dot) Walsh" <gjwalsh(at)dscdirectionalservices(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: scope of connection id (handler)
Date: 2008-09-19 02:14:42
Message-ID: 1221790482.26591.11.camel@www.dscdirectionalservices.com (view raw or flat)
Thread:
Lists: pgsql-novice
I've completed pseudo code for php script.

Simply, the initial script is called when the user completes specified
tasks, in this case a conditional group of up to 14. The script
interprets requirements and calls the appropriate scoring function.

Each function accesses a table, massages data, and writes the results
into another table. Straightforward stuff.

My question .... pg_connect is established in the main script. Does a
new connect have to made within each function?  That's what I was doing
to prove the program workings at the function level, but now it is time
to tie it all together.

My confusion arises from the id being placed in $pg. How will/should/
must that be made available within the function so it can do its job?
Should it be passed?  Declared as a global within the function? or must
I establish separate in-and-out-connections within each function?



pgsql-novice by date

Next:From: A BDate: 2008-09-19 07:11:45
Subject: How do create a user with a bashscript
Previous:From: Harold A. Giménez Ch.Date: 2008-09-18 23:46:25
Subject: Re: Moving data from one set of tables to another?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group