On Fri, 2006-06-16 at 08:27 -0400, John DeSoi wrote: > On Jun 15, 2006, at 11:49 AM, chester c young wrote: > > > in PHP for example, where there are multiple sessions and which you > > get is random: > > > > how do you know if the session you're in has prepared a particular > > statement? > > > > and/or how do you get a list of prepared statements? > > > > last, is there any after login trigger that one could use to > > prepare statements the session would need? or is this a dumb idea? > > If you are using pooled connections, I don't think there is a > reasonable way you could managed prepared statements across requests. > You'll probably want to just prepare the ones you need for the > current request and discard them when the request ends.
Temporary tables. BEGIN; SAVEPOINT; SELECT * FROM temporary_prepared_statement; ROLLBACK TO SAVEPOINT < on failure>; CREATE TEMPORARY TABLE temporary_prepared_statement ...; COMMIT; Now you have a place to store and retrieve prepared connection state for the lifetime of the database backend provided PHP doesn't remove temporary tables on the connection. > I have a short article where you might find some useful information > for managing prepared statements: > > http://pgedit.com/resource/php/pgfuncall > > You might also post your question to PostgreSQL PHP list -- probably > more PHP expertise there. > > Best, > > John > > > > > John DeSoi, Ph.D. > http://pgedit.com/ > Power Tools for PostgreSQL > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > -- ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
