Re: Early binding of CURRENT_SCHEMA (Was: CREATE FUNCTION ... SEARCH {, DEFAULT | SYSTEM | SESSION })

2023-09-27 Thread dld
On 27-09-2023 04:03, Erik Wienhold wrote: ccing list On 2023-09-27 00:12 +0200, dld write: On 26-09-2023 23:47, Erik Wienhold wrote: On 2023-09-26 14:44 +0200, dld wrote: I followed the discussion about the schema resolution, and I really think there is need for an early bound (at function

Re: Early binding of CURRENT_SCHEMA (Was: CREATE FUNCTION ... SEARCH {, DEFAULT | SYSTEM | SESSION })

2023-09-26 Thread Erik Wienhold
ccing list On 2023-09-27 00:12 +0200, dld write: > On 26-09-2023 23:47, Erik Wienhold wrote: > > On 2023-09-26 14:44 +0200, dld wrote: > > > I followed the discussion about the schema resolution, and I really think > > > there is need for an early bound (at function definition time) version of >

Re: Early binding of CURRENT_SCHEMA (Was: CREATE FUNCTION ... SEARCH {, DEFAULT | SYSTEM | SESSION })

2023-09-26 Thread Erik Wienhold
On 2023-09-26 14:44 +0200, dld wrote: > I followed the discussion about the schema resolution, and I really think > there is need for an early bound (at function definition time) version of > CURRENT_SCHEMA (the first member of search_path) You mean something like CREATE FUNCTION

Early binding of CURRENT_SCHEMA (Was: CREATE FUNCTION ... SEARCH {, DEFAULT | SYSTEM | SESSION })

2023-09-26 Thread dld
Hi there! I followed the discussion about the schema resolution, and I really think there is need for an early bound (at function definition time) version of CURRENT_SCHEMA (the first member of search_path) Avoiding hard-coding of schema names, (and avoiding polluting the actual users