Happy New Year to you and thanks again
Wilma
--- Ursprüngliche Nachricht ---
Von: Adrian Klaver
Datum: 30.12.2023 19:05:28
An: Wilma Wantren
Betreff: Re: Changing a schema's name with function1 calling function2
On 12/30/23 08:01, Wilma Wantren wrote:
> Thank you all, and especially you, Ad
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
es no change to the search_path would
be necessary after renaming the schema.
Many thanks for the reference to sqitch, I'll have a look at that now.
Translated with DeepL.com (free version)
--- Ursprüngliche Nachricht ---
Von: Adrian Klaver
Datum: 23.12.2023 01:09:12
An: Wilma Wantren
B
uld
be the value of the function's search_path in the function's meta data. This
variable, e.g. "$function_schema" would still denote the correct schema after
renaming the schema.
--- Ursprüngliche Nachricht ---
Von: Adrian Klaver
Datum: 21.12.2023 17:30:02
An: Wilma Wantren ,
Now as text mail, sorry.
I accidentally posted the following to the bugs mailing list first. Sorry for
this, now as a question here.
The company I work for used to only use Oracle databases for their program and
now also supports PostgreSQL.
With Postgres, we create a database, a user and a schem
I accidentally posted the following to the bugs mailing list first. Sorry for this, now as a question here.The company I work for used to only use Oracle databases for their program and now also supports PostgreSQL.With Postgres, we create a database, a user and a schema, which all have the same n
