That's really nice of you to point me to this mailing list! I'll make my
suggestion there in the next few days.
I don't think it's so bad if the new feature is not available until fall 2024
or even later, the time in which it's useful would be very long in any case.
Happy New Year to you and than
Thank you all, and especially you, Adrian, for your answers.
However, I find the last suggestion too complicated. In Peter's words I had
suggested a "magic variable" __function_schema__ which can be set as the
search_path of a function to select - when executing the function - the schema
the fun
Great that you have discussed this further! And sorry that what I wrote is
apparently still misleading.
Peter understood me correctly, "__function_schema__ always refers to the schema
the function actually is in".
I define:
1. create function my_schema.function1...
2. alter function function1 s
Thank you!
I had already feared that such a variable does not exist (because I had not
found it). I think that's a pity, because I suspect that in at least 90% of the
cases where a function needs a search_path, this variable would be the value of
the search_path, so that in 90% of the cases no c
Thank you for your response!
No, this does not help me. I will try to explain better what I mean. Our
customers use our program with a Postgres database, user and schema, which have
the same name. The customer chooses the name. Let's say one customer calls the
database, user and schema 'my_thin
