Re: review: CHECK FUNCTION statement
Albe Laurenz <laurenz.albe@wien.gv.at>
From: "Albe Laurenz" <laurenz.albe@wien.gv.at>
To: "Pavel Stehule *EXTERN*" <pavel.stehule@gmail.com>
Cc: "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
Date: 2011-12-13T10:01:27Z
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
Pavel Stehule wrote: >> One thing I forgot to mention: >> I thought there was a consensus to add a WITH() or OPTIONS() clause >> to pass options to the checker function: >> http://archives.postgresql.org/message-id/12568.1322669638@sss.pgh.pa.us >> >> I think this should be there so that the API does not have to be >> changed in the future. >> > there is just one question - how propagate options to check functions > > I am thinking about third parameter - probably text array Either that, or couldn't you pass an option List as data type "internal"? I don't know what is most natural or convenient. Yours, Laurenz Albe