plPHP -- sort of an announcement.. but not commercial

On Fri, 2003-08-01 at 19:06, Joshua D. Drake wrote:

Hello,

As a recent flurry of activity has commenced within Command Prompt we
have released
upon this rather unround earth, plPHP. Yes it is trigger safe, yes you
can write UDF's in
PostgreSQL with PHP now.

Find it here:

http://www.commandprompt.com/entry.lxp?lxpe=260

Is there a possibility of getting this in v7.5?

-- 
+-----------------------------------------------------------------+
| Ron Johnson, Jr.        Home: ron.l.johnson@cox.net             |
| Jefferson, LA  USA                                              |
|                                                                 |
| "I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!"                                    |
|    unknown                                                      |
+-----------------------------------------------------------------+

On Fri, Aug 01, 2003 at 05:06:00PM -0700, Joshua D. Drake wrote:

Hello,

As a recent flurry of activity has commenced within Command Prompt we
have released
upon this rather unround earth, plPHP. Yes it is trigger safe, yes you
can write UDF's in
PostgreSQL with PHP now.

Very nice.

Is it in the public domain? I don't see any copyright nor license
mention in the source code...

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"In Europe they call me Niklaus Wirth; in the US they call me Nickel's worth.
That's because in Europe they call me by name, and in the US by value!"

This is very exciting, is this stable, production ready, etc?

Gavin

Alvaro Herrera wrote:

Hello,

Well PHP is GPL... thus we left it GPL... it belongs to the
community. Enjoy :)

J

Alvaro Herrera wrote:

Hello,

I am in final testing now, so feel free to download the static. It is
a pain in the but to compile (static is Linux). By the end of the week
it should be all pacakaged etc...

J

Gavin M. Roy wrote:

Uh, PHP isn't GPL, as of PHP4, http://www.php.net/license/

Q. Why is PHP 4 not dual-licensed under the GNU General Public License
(GPL) like PHP 3 was?

A. GPL enforces many restrictions on what can and cannot be done with
the licensed code. The PHP developers decided to release PHP under a
much more loose license (Apache-style), to help PHP become as popular as
possible.

I have attached the license that came with PHP 4.0.4.

---------------------------------------------------------------------------

Joshua D. Drake wrote:

Hello,

Well PHP is GPL... thus we left it GPL... it belongs to the
community. Enjoy :)

J

Alvaro Herrera wrote:

On Fri, Aug 01, 2003 at 05:06:00PM -0700, Joshua D. Drake wrote:

Hello,

As a recent flurry of activity has commenced within Command Prompt we
have released
upon this rather unround earth, plPHP. Yes it is trigger safe, yes you
can write UDF's in
PostgreSQL with PHP now.

Very nice.

Is it in the public domain? I don't see any copyright nor license
mention in the source code...

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Bruce Momjian <pgman@candle.pha.pa.us> writes:

Uh, PHP isn't GPL, as of PHP4, http://www.php.net/license/

Consider also that if you have hopes of plPHP someday being included in
the standard Postgres distribution, it'll need to be BSD-licensed.

(Including PLs in the standard distro strikes me as a good idea, BTW.
They usually need maintenance along with the core backend code.)

regards, tom lane

On Fri, 1 Aug 2003, Joshua D. Drake wrote:

I am in final testing now, so feel free to download the static. It is
a pain in the but to compile (static is Linux). By the end of the week
it should be all pacakaged etc...

Will this compile in any environment where PHP is installed?
ie. FreeBSD

Will this compile in any environment where PHP is installed?
ie. FreeBSD

Well it is only tested on Linux but there is no reason to think it
wouldn't compile on any unix that was gcc based.

Dear all
I was waiting for this type of product but will plPHP turn to be like LXP

also does it support all the PHP4 syntax

Regards,
V Kashyap

----- Original Message -----
From: "Francisco J Reyes" <fran@natserv.net>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: "Gavin M. Roy" <gmr@bteg.net>; <pgsql-general@postgresql.org>
Sent: Sunday, August 03, 2003 00:04
Subject: Re: [GENERAL] plPHP -- sort of an announcement.. but not commercial

On Fri, 2003-08-01 at 21:08, Ron Johnson wrote:

On Fri, 2003-08-01 at 19:06, Joshua D. Drake wrote:

Hello,

As a recent flurry of activity has commenced within Command Prompt we
have released
upon this rather unround earth, plPHP. Yes it is trigger safe, yes you
can write UDF's in
PostgreSQL with PHP now.

Find it here:

http://www.commandprompt.com/entry.lxp?lxpe=260

Is there a possibility of getting this in v7.5?

Heres the things I think would have to happen to put this in 7.5

1) Resolve license issues (not bsd licensed)
2) Integrate it into the postgresql build system so it can work on all
platforms.
3) Make it build against different versions of php
4) More people testing it in different situations.

FWIW I tried installing it on a system over the weekend, the trigger
feature seemed to work, and the complex array example function seemed to
work ok, but the basic simple echo example failed. I've subscribed to
the mailing lists, so we'll see if I can figure out where I went wrong.

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

Any chance that PHP in safe mode meets our requirements for a trusted
language? It would be nice to have both php and phpu as two different
choices.

On Fri, 1 Aug 2003, Joshua D. Drake wrote:

Robert Treat wrote:

On Fri, 2003-08-01 at 21:08, Ron Johnson wrote:

Is there a possibility of getting this in v7.5?

Heres the things I think would have to happen to put this in 7.5

1) Resolve license issues (not bsd licensed)
2) Integrate it into the postgresql build system so it can work on all
platforms.
3) Make it build against different versions of php
4) More people testing it in different situations.

Here's my list.

Minor issues/ general code cleanup:
1. eliminate '//' style comments
2. fix indentation

More significant:
2. Add support for array conversion in-out
3. Add support for set-returning functions
4. Add support for argument/return-value polymorphism
5. Incorporate recent improvements in function caching (ala PL/pgSQL)
6. Add documentation
7. Add regression test support
8. Modify for new ereport syntax and nested error contexts

Most significant:
9. Use PHP embed API instead of the PHP CLI (command line interface)
10.Fix license

Joe

On Mon, 4 Aug 2003, Joe Conway wrote:

Robert Treat wrote:

On Fri, 2003-08-01 at 21:08, Ron Johnson wrote:

Is there a possibility of getting this in v7.5?

Heres the things I think would have to happen to put this in 7.5

1) Resolve license issues (not bsd licensed)
2) Integrate it into the postgresql build system so it can work on all
platforms.
3) Make it build against different versions of php
4) More people testing it in different situations.

Here's my list.

Minor issues/ general code cleanup:
1. eliminate '//' style comments
2. fix indentation

More significant:
2. Add support for array conversion in-out
3. Add support for set-returning functions
4. Add support for argument/return-value polymorphism
5. Incorporate recent improvements in function caching (ala PL/pgSQL)
6. Add documentation
7. Add regression test support
8. Modify for new ereport syntax and nested error contexts

Most significant:
9. Use PHP embed API instead of the PHP CLI (command line interface)
10.Fix license

Looking at the license for PHP found here:

http://www.php.net/license/3_0.txt

it would seem to be pretty much an apache style license that doesn't allow
you to relicense it without permission. but it looks BSD compatible.

scott.marlowe wrote:

10.Fix license

Looking at the license for PHP found here:

http://www.php.net/license/3_0.txt

it would seem to be pretty much an apache style license that doesn't allow
you to relicense it without permission. but it looks BSD compatible.

The issue was that plPHP as posted was claimed to be GPL, although there
isn't any notice at all in the source that I saw.

Does the PHP license require programs that dynamically link carry their
license, similar to GPL (I didn't get that impression)? If not, then
something like PL/PHP should be licensable under BSD.

Joe

On Mon, 4 Aug 2003, Joe Conway wrote:

scott.marlowe wrote:

10.Fix license

Looking at the license for PHP found here:

http://www.php.net/license/3_0.txt

it would seem to be pretty much an apache style license that doesn't allow
you to relicense it without permission. but it looks BSD compatible.

The issue was that plPHP as posted was claimed to be GPL, although there
isn't any notice at all in the source that I saw.

Does the PHP license require programs that dynamically link carry their
license, similar to GPL (I didn't get that impression)? If not, then
something like PL/PHP should be licensable under BSD.

Yeah, I'm pretty sure it's safe to link to. We could always as the PHP
guys themselves to be sure.

Hello,

How do you mean to be like LXP?

J

Aspire wrote:

1) Resolve license issues (not bsd licensed)

We can make it any license we want... Right now it is PHP licensed just
because that is what seemed to make sense.

2) Integrate it into the postgresql build system so it can work on all
platforms.

That is up to the core.

3) Make it build against different versions of php

We don't believe it should support ANYTHING but 4.3.2 or above.

4) More people testing it in different situations.

Makes sense.

Here's my list.

Minor issues/ general code cleanup:
1. eliminate '//' style comments

Our programmers prefer // style comments.

More significant:
2. Add support for array conversion in-out
3. Add support for set-returning functions
4. Add support for argument/return-value polymorphism
5. Incorporate recent improvements in function caching (ala PL/pgSQL)
6. Add documentation
7. Add regression test support
8. Modify for new ereport syntax and nested error contexts

These are all good suggestions. Anybody want to help? plPHP was done
as a proof of concept more than anything else. We are concentrating
our efforts on other things.

On Mon, 4 Aug 2003, Joshua D. Drake wrote:

2) Integrate it into the postgresql build system so it can work on all
platforms.

That is up to the core.

Actually, not really ... with erserver, I pulled down the various build
files for the various platforms, so that *in theory* it will build under
anything that PostgreSQL supports ...

3) Make it build against different versions of php

We don't believe it should support ANYTHING but 4.3.2 or above.

So, it builds against PHP5? :) Humor aside, though, I imagine there are a
fair # of ISPs out there that still haven't gone above 4.1 ... the latest
PgMarket "dev version" only just drop'd 4.0 support ...