On 09/15/2014 11:00 AM, Rob Sargent wrote:
On 09/15/2014 11:49 AM, cowwoc wrote:
Hi Pavel,
On 15/09/2014 1:40 PM, Pavel Stehule wrote:
The main drivers are:
1. Not having to learn yet another language. I find the
expressiveness and readability of the other scripting
languages very clunky compared to Java.
Gili
I've seen too many good java developers write too much terrible
database-oriented code. If they are good with db and sql, plpgsql will
not be a problem to learn.
Agreed, plpgsql is SQL with Postgres extensions. I went down this road
with plpythonu. I am comfortable in Python, so I thought it would be
easier to write functions using plpythonu. I actually did this
backwards. I had created a fairly complex function in plpgsql and I
figured I could simplify by using plpythonu. I was well into it when I
had realized I written more code in plpythonu than plpgsql and still was
not close to completing it. I still use plpythonu but only when I need
the dynamic nature of Python or really need to use some Python module.
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
