Honestly, I don't know if it would be popular enough on its own. Now the plPerlNG that AndrewSo, why tie it into the PostgreSQL source tree? Won't it be popular enough to live on its own, that it has to be distributed as part of the core?
and us are working, yes but plPHP? It is nifty, it is cool, it is very capable but it is still PHP.
I think the point of having it in core is that the three most popular user space languages are:
Python Perl PHP
If those are covered within core under the pl* then we have all bases covered.
I am not saying that it should be in core (although I definately think plPerlNG should be). This all
started because it was suggested it could be :)
J
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
-- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
