> I find the whole argument that, lack of an untrusted version of the PL
> means it should be deprecated, crazy. There are plenty of situations
> where you don't care that the PL is untrusted.
Yes you are absolutely correct. However my argument was more than that.
It contained:
The fact that it was only untrusted
Not moving forward. plPython is basically in a static state, I can't do
(AFAIK) in plPython today that I couldn't do 2 years ago.
PostgreSQL is moving forward at an increasing rate. The pl languages
that are in core should at least try to keep up with the feature set.
Also there is the maintainability perspective. I may write a one time
function in plpython because python is my prefered language. I would not
however use it as my primary language for procedures because it can't be
trusted.
Believe me, if plPython could be trusted I would be all over anyone who
suggested deprecating it. Python is my preferred language.
Sincerely,
Joshua D. Drake
>
> Joe
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
