Re: Bug in SQL/MED?
От
Tom Lane
Тема
Re: Bug in SQL/MED?
Дата
Msg-id
1131.1309906086@sss.pgh.pa.us
Ответ на
Re: Bug in SQL/MED? (Tom Lane)
Список
Дерево обсуждения
Bug in SQL/MED? "Albe Laurenz" <laurenz.albe@wien.gv.at>
Re: Bug in SQL/MED? 花田 茂<hanada@metrosystems.co.jp>
Re: Bug in SQL/MED? Alvaro Herrera <alvherre@commandprompt.com>
Re: Bug in SQL/MED? Shigeru Hanada <shigeru.hanada@gmail.com>
Re: Bug in SQL/MED? Tom Lane <tgl@sss.pgh.pa.us>
Re: Bug in SQL/MED? Robert Haas <robertmhaas@gmail.com>
Re: Bug in SQL/MED? Tom Lane <tgl@sss.pgh.pa.us>
Re: Bug in SQL/MED? Tom Lane <tgl@sss.pgh.pa.us>
Re: Bug in SQL/MED? Tom Lane <tgl@sss.pgh.pa.us>
Re: Bug in SQL/MED? "Albe Laurenz" <laurenz.albe@wien.gv.at>
Re: Bug in SQL/MED? "Albe Laurenz" <laurenz.albe@wien.gv.at>
I wrote:
> Another possibility that just occurred to me is to call the validator
> like this:
>
> if (OidIsValid(fdwvalidator))
> {
> Datum valarg = result;
>
> /* pass a null options list as an empty array */
> if (DatumGetPointer(valarg) == NULL)
> valarg = construct_empty_array(TEXTOID);
> OidFunctionCall2(fdwvalidator, valarg, ObjectIdGetDatum(catalogId));
> }
> This would avoid messing with the semantics of empty options lists
> throughout foreigncmds.c, and also avoid requiring validators to deal
> with null arguments.
Not hearing any objections, I've fixed it that way.
regards, tom lane
В списке pgsql-hackers по дате отправления
