Re: Error prone compilation of stored procedure

2015-07-06 13:52 GMT+02:00 pinker <pinker(at)onet(dot)eu>:

> Pavel Stehule wrote
> > PLpgSQL doesn't check a identifiers inside embedded SQL before execution.
> > In this case j_var can be theoretically some SQL identifiers - the
> > possibility or impossibility is not know in function validation stage.
> >
> > It has some plus and minus points. The plus - there are not strong
> > dependency between database objects and PL code. The minus - lot of bugs
> > are not detected in validation stage. But this issue can be solved by
> > plpgsql_check extension https://github.com/okbob/plpgsql_check/
>
> Thank you for the link to extension.
> Another minus is that my colleagues which use to work on oracle think that
> postgresql is at least one league below oracle.
>

why minus? - The dependency in PL/SQL is hell - it strongly increase a
complexity of lot of tasks. The plpgsql is designed to be simple as
possible - but it has the power of PL/SQL. If you need to check your
PLpgSQL code, just install plpgsql_check extension.

Regards

Pavel

>
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/Error-prone-compilation-of-stored-procedure-tp5856699p5856708.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>