Re: review: CHECK FUNCTION statement
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Albe Laurenz <laurenz.albe@wien.gv.at>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-30T18:21:54Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add const qualifiers to node inspection functions
- d5f23af6bfbc 9.2.0 cited
Hello I rechecked a possibility to use a validator function together with checker function. The main issue is a different interface of both functions. Validator needs just function oid and uses global variable check_function_bodies. Checker function needs function oid and relation oid (possible some other params). When we mix these two functions together we need a validator(oid) or validator(oid, oid, variadic "any") one parameter function is old validator, three parameters function is checker. Question: What is a correct signature for this function? We cannot use a overloading, because we can have only one validator function per language. We can change a validator to support both forms, and we have to be carefully and correct if we will work with our validators(3 and more params) or foreign validators (1 param). We should to support both (compatibility reasons). We are not careful about validators now - there are some places, where one parameter is hardly expected - this should be changed. So using validator for checking doesn't mean smaller patch, but is true, so these functions has similar semantic - validator is usually "low level" checker. What is your opinion? Regards Pavel