| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Possible trigger bug? function call argument literalised |
| Date: | 2021-01-03 18:32:13 |
| Message-ID: | c2cd33a6-6cbf-649e-140e-4deed1783482@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/3/21 10:27 AM, Thiemo Kellner wrote:
>
> Quoting Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
>
>>> Well, I guess, I can put the correct schema at installation, but
>>> would have liked to have a more general approach. Furthermore, I
>>> think this also implies that installation can only be done by psql. :-s
>>
>> Why not grab the CURRENT_SCHEMA in the function?:
>>
>> DECLARE
>> V_COUNT smallint;
>> C_SCHEMA varchar := CURRENT_SCHEMA;
>
> Thank you all for your lightning fast replies. I failed to set it at
> install time. \gset cannot be used as bind variables in SQL. So, I try
> retaining the restriction to that the function needs to be installed in
> the same schema as the triggered table.
>
Alright you lost me.
Can you provide an outline form of what you are trying to accomplish?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thiemo Kellner | 2021-01-03 19:19:14 | Re: Possible trigger bug? function call argument literalised |
| Previous Message | Thiemo Kellner | 2021-01-03 18:27:41 | Re: Possible trigger bug? function call argument literalised |