| From: | pinker <pinker(at)onet(dot)eu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Error prone compilation of stored procedure |
| Date: | 2015-07-06 11:52:52 |
| Message-ID: | 1436183572684-5856708.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
--
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2015-07-06 12:02:24 | Re: Error prone compilation of stored procedure |
| Previous Message | pinker | 2015-07-06 11:43:02 | Re: Error prone compilation of stored procedure |