From: Rory Campbell-Lange <rory@campbell-lange.net>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: Advocacy (PostgreSQL) <pgsql-advocacy@postgresql.org>
Cc: PostgreSQL-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] interesting PHP/MySQL thread
Date: Tue, 24 Jun 2003 13:59:33 +0100
Message-ID: <20030624125933.GD11929@campbell-lange.net> (raw)
In-Reply-To: <200306222159.h5MLxT720807@candle.pha.pa.us>
References: <200306211146.41852.josh@agliodbs.com>
<200306222159.h5MLxT720807@candle.pha.pa.us>
I'm a Postgres and PHP newbie. I'm having a great deal of success with
my latest development effort having moved most of the logic from a
perl/php logic 'core' to postgres using plpgsql functions. (Thanks for
all that help, Josh).
I have a few comments to make on the idea of introducing people, PHP
developers especially, to postgresql. I'm not commenting here on how
easy it is to use PHP with postgres (it was transparent for me using
Debian) or whether or not to advocate the use of advanced features to
general users. Rather, it appears to me, that the PHP/Postgres
documentation and feature set should be improved.
1) PHP Documentation
The postgresql "write up" in the PHP html documentation doesn't give
a very good picture of the capabilities of postgres. While the PHP
docs aren't obviously a good place to write up the benefits of
plpgsql functions, some mention should be made to help differentiate
between the capabilities of MySQL and Postgres.
PHP documents:
ref.pgsql.html; ref.mysql.html
The MySQL examples given for database specific functions are useful
and to the point. The page on most of the Postgres functions are
sketchy. (No error number in Postgres...)
PHP documents:
function.mysql-errno.html; function.pg-result-error.html
PHP/Postgres provides a set of predefined constants, eg
PGSQL_COMMAND_OK and PGSQL_FATAL_ERROR. The use and parameters of
these constants is not described. The latter appears to provide
inconsistent results under my PHP 4.2.3 install.
2) PHP<->Postgres bugs
Apart from the PGSQL_FATAL_ERROR problem above, it would be good to
find a more simple, PHP-like, approach to catch exceptions and the
like. At the moment I believe one has to do something like:
function test () {
$sql = "
SELECT
count(n_id) as number
FROM
people
";
ob_start();
$result = pg_exec ($this->conn, $sql);
$this->status = pg_result_status($result);
ob_end_clean();
$this->result_checker();
if ($this->error != 0) {
echo "An error occured.\n";
exit;
}
...
return $this;
}
function result_checker () {
// horrible code to check for postgres exceptions
// status numbers sometimes show up
// ghosts of PGSQL_FATAL_ERROR?
if (! isset($this->status) or
($this->status == 5 or $this->status == 7)) {
$this->error = 1;
// wierdly, this always works
$this->error_msg = pg_last_error($this->conn);
return 1;
} else {
return 0;
}
}
On 22/06/03, Bruce Momjian (pgman@candle.pha.pa.us) wrote:
> We need to use this opportunity to encourage PHP folks to switch to
> PostgreSQL.
--
Rory Campbell-Lange
<rory@campbell-lange.net>
<www.campbell-lange.net>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: rory@campbell-lange.net, pgman@candle.pha.pa.us, josh@agliodbs.com, mail@joeconway.com, pgsql-advocacy@postgresql.org, pgsql-general@postgresql.org
Subject: Re: [GENERAL] interesting PHP/MySQL thread
In-Reply-To: <20030624125933.GD11929@campbell-lange.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox