Re: Re: [HACKERS] How to print explain using PHP

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: pgman(at)candle(dot)pha(dot)pa(dot)us
Cc: zakkr(at)zf(dot)jcu(dot)cz, martin(at)math(dot)unl(dot)edu(dot)ar, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [HACKERS] How to print explain using PHP
Date: 2001-01-10 01:58:59
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general pgsql-hackers

> > On Tue, 9 Jan 2001, Bruce Momjian wrote:
> >
> > > I think the issue here was that these functions don't make any sense for
> > > PHP because you can't register C functions.
> >
> > I mean (I know) that you can register some common (internal) PHP
> > function and this function can call your PHP function. It is some used in
> > XML Expat parser that use element handlers (functions).
> >
> > It's very good resolvable in PHP... see php-4.0b3/ext/xml/xml.c as example

IMHO it would be confusing for PHP users. What about changing the PHP
function php_pgsql_do_connect so that it calls PQsetNoticeProcessor to
preserve the last NOTIFY string somewhere. And we would invent new PHP
function pg_notifymessage (or whatever) to extract the string later on.

> OK, this is why I never added it to the TODO list. Should we add this
> to our TODO list?

I don't think so, if the TODO should only include things to do with
the PostgreSQL source code.
Tatsuo Ishii

In response to

Browse pgsql-general by date

  From Date Subject
Next Message rob 2001-01-10 02:00:10 Re: trouble with db-restore
Previous Message Joseph Shraibman 2001-01-10 01:55:09 Re: xml middleware

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-01-10 02:32:00 Re: Well, we seem to be proof against cache-inval problems now
Previous Message Tom Lane 2001-01-10 00:45:01 Re: BETWEEN [SYMMETRIC | ASYMMETRIC]