Re: poll: CHECK TRIGGER?

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Peter Eisentraut <peter_e@gmx.net>, Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@commandprompt.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2012-03-10T12:35:12Z

Lists: pgsql-hackers

Attachments

plpgsql_check_function.diff.gz (application/x-gzip) patch

Hello

2012/3/10 Tom Lane <tgl@sss.pgh.pa.us>:
> Peter Eisentraut <peter_e@gmx.net> writes:
>> But then I would have to map all language-specific error reports to some
>> SQL error scheme, which is not only cumbersome but pretty useless.  For
>> example, a Python programmer will be familiar with the typical output
>> that pylint produces and how to fix it.  If we hide that output behind
>> the layer of SQL-ness, that won't make things easier to anyone.
>
> Yeah, this is a good point.  I'm willing to concede that we are not
> close to having a uniform API that could be used for checker functions,
> so maybe what we should do for now is just invent
> plpgsql_check_function(regprocedure).  I'd still like to see the
> question revisited sometime in the future, but it would be appropriate
> to have a few working examples of popular checker functions for
> different languages before we try to invent a common API.
>

here is draft

I removed all generic structures.

Regards

Pavel


>                        regards, tom lane