| From: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: plperl strict mode |
| Date: | 2005-05-24 16:15:15 |
| Message-ID: | 20050524161515.GF8743@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Tue, May 24, 2005 at 11:53:45AM -0400, Andrew Dunstan wrote:
> Alvaro Herrera wrote:
>
> >On Sat, May 21, 2005 at 04:04:36PM -0400, Andrew Dunstan wrote:
> >
> >Hmm, is there a way to have a validator function and have the strict
> >check at function creation too? I know these things are reported with
> >perl -c, not sure if they can be reached with the C interface.
>
> Maybe I have missed it, but I don't see an exposed interface that is
> called when we create a function, only one to set up the interpreter and
> one where we call the function (which compiles it if it isn't already
> compiled).
Yes, you can register a function as "validator" during language
creation. AFAIR there are no validator functions except SQL and
plpgsql, so you would have to create one for plperl ...
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2005-05-24 16:15:26 | Re: [PATCH] pg_autovacuum commandline password hiding. |
| Previous Message | Alvaro Herrera | 2005-05-24 16:10:00 | Re: numeric precision when raising one numeric to another. |