Re: [Feature Request] Schema Aliases and Versioned Schemas - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: [Feature Request] Schema Aliases and Versioned Schemas
Date
Msg-id CAExHW5sErBoUhJJnRaP+epo55_+niDm=Gu10WDCkyYmLOsaezg@mail.gmail.com
Whole thread Raw
In response to [Feature Request] Schema Aliases and Versioned Schemas  (AbdelAziz Sharaf <mickelpower75@gmail.com>)
Responses Re: [Feature Request] Schema Aliases and Versioned Schemas
List pgsql-hackers
On Wed, Nov 27, 2024 at 8:45 PM AbdelAziz Sharaf
<mickelpower75@gmail.com> wrote:
>
> Dear PostgreSQL Development Team,
>
> I’d like to propose a new feature for consideration: schema aliases and versions
>
> **Problem Statement:**
> For migrating old db to new one, one must use an external tool or define a dedicated migration script where all
possibleissues could arise 
>
> **Proposed Solution:**
> there is two ways I may think about
> - versioned schemas : where every version act as a separate schema and the `latest` one or the one the program
requestis the one in use and each new schema could inherit a table, index, view, ... without additional data 
> - aliases : where every new schema is defined and migrated separately then an alias is set for the one in use

Isn't this same as adding the required schema name in the search_path?

--
Best Wishes,
Ashutosh Bapat



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY
Next
From: Peter Eisentraut
Date:
Subject: Re: tab_complete for copy(merge