On Nov 19, 2009, at 11:32 AM, Peter Eisentraut wrote:
> But you wouldn't, for example, get away with breaking SQL (or even
> improving it incompatibly) to facilitate a better elog.
This doesn't fit the situation.
I'm not breaking PL/Python. I'm trying to add PL/Python3. =)
> I think of a PL/Python function as a Python script file stored
> in the database.
For Python, I think that's a mistake. Python scripts are independent applications.
[tho, I think this does illuminate our perspectives...]
