From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: when to use "execute" in plpgsql? |
Date: | 2009-03-01 15:18:15 |
Message-ID: | 162867790903010718v77f238bfu29a4d5d62e93fe6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
>
> My experience in this is just from 8.0 so I don't know if anything has
> changed. In general, if tables are created or deleted within the
> function then you want to use execute, as well as if the tables are
> recreated in the course of a normal workflow. For example, if you have a
> table that you regenerate once a day (by drop and create) you will not
> want to reference that table in a view or function.
this bug is solved in 8.3
regards
Pavel Stehule
>
> Obviously if you want to run dynamic code you also need to use execute.
>
> Sim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmqnSkACgkQjDX6szCBa+o77gCgjB7W+4tIYZVPtEvaF1Uj3QBC
> fPcAoOubAAC9dr5opTRyFsyUfLq6ojQF
> =q5NU
> -----END PGP SIGNATURE-----
>
> --
> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sim Zacks | 2009-03-01 15:21:16 | Re: function to return rows as columns? |
Previous Message | Sim Zacks | 2009-03-01 14:35:21 | Re: when to use "execute" in plpgsql? |