Thread: Re: [HACKERS] How to print explain using PHP
> > 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 OK, this is why I never added it to the TODO list. Should we add this to our TODO list? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
On Tue, 9 Jan 2001, Bruce Momjian wrote: > > > > 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 > > OK, this is why I never added it to the TODO list. Should we add this > to our TODO list? > Quick look to PHP:-) libphp/zend_execute_API.c: call_user_function() Karel
> > 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