You can think of a database as a filesystem as well. That is do some processing, store the result in temp table, do some more, etc,etc then merge and process temp tables to arrive at some result.
Just as in the case of filesystem, if you are operating in a concurrent evironment, you need to fence against that. That is it is possible that at a given time two sessions will arrive at the same processing point where they need to create such temp tables.
The other solution which I prefer is to write a stored procedure to solve this. Or get creative with nested and complex SQL queries.
Cheers
Medi
On 8/20/07, giuseppe.derossi@email.it <giuseppe.derossi@email.it> wrote:
Hi all,
I use Postgresql 8.2 in win env. I wrote a set of complex queries which
return three temporary tables of results. I want to use then in php, but the
unique way I know consists on sending one query a time via php, the logic I
need has now been cablated into the sql code.
I could use the functions but it seems a bit long becouse I set some
temporary tables and I shoud use dynamic queries and I've more then a
recordset.
Is there a way to store this piece of sql code into the database and to
recall it with the right input by php and to read only the two tables of
results via PHP?
thanks in advantage
giu
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
In REGALO un GIOCO! Scegli GPBikes 3D,Bubble Boom, Rock City Empire
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=6732&d=20070820
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq