Message-ID: <3A49F2A7.77CEE0E1@mohawksoft.com>
Date: Wed, 27 Dec 2000 08:46:15 -0500
From: mlw <markw@mohawksoft.com>
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: PHP and PostgreSQL
References: <200012270556.AAA19258@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:
> 
> I have been asked by the major PHP developer Rasmus Lerdorf to see if
> the PostgreSQL/PHP interface needs any improvements.
> 
> Is the current PostgreSQL interface module in PHP adequate?  Does it
> support all the current libpq features?
> 
> If not, would someone submit some patches to the PHP folks.  They want
> us to work well with PHP.  They are basically encouraging us to improve
> it in any way we can.

In a current project, I am using Postgres, Oracle, and PHP. I think
PHP's API is very complete and usable, I can't think of anything we've
run into that was a result of PHP lacking a feature.

The only thing I'd like to see would be an Oracle construct moved to
Postgres. The idea that we can "prepare" a statement then execute it
multiple times without going through the planner more than once. This
would also require the ability to create and set arbitrary variables in
a Postgres session. 

Since these are programmatic queries, only a handful of different SQL
queries are ever executed. The ability to cache the planned query tree
(is this the right terminology?) in a shared block, and simply reuse it,
in the multiple back-ends, with a new variable value, would speed up
some of the more complex queries, I guess.

-- 
http://www.mohawksoft.com