X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8F399D1B565 for ; Sun, 2 Nov 2003 01:46:43 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 25418-10 for ; Sat, 1 Nov 2003 21:46:15 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 06B84D1B55D for ; Sat, 1 Nov 2003 21:46:12 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id hA21kBNu077687 for ; Sun, 2 Nov 2003 01:46:11 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id hA21UYlX075813 for pgsql-php@postgresql.org; Sun, 2 Nov 2003 01:30:34 GMT From: ljb X-Newsgroups: comp.databases.postgresql.interfaces.php Subject: Re: Support for prepared queries Date: Sun, 2 Nov 2003 01:30:34 +0000 (UTC) Organization: Hub.Org Networking Services Lines: 8 Message-ID: References: <200310241850.56494.martin@bugs.unl.edu.ar> X-Complaints-To: usenet@news.hub.org X-No-Archive: yes User-Agent: slrn/0.9.8.0 (Linux) To: pgsql-php@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/1 X-Sequence-Number: 2394 jleelim@xxxxxx.com 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? Maybe use a procedure-language function instead of a prepared query? Persistent connections won't help; the prepared query may still be valid but only for that web-server child process.