Re: [Feature Request] Schema Aliases and Versioned Schemas

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: AbdelAziz Sharaf <mickelpower75(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Feature Request] Schema Aliases and Versioned Schemas
Date: 2024-11-28 11:10:08
Message-ID: CAExHW5sErBoUhJJnRaP+epo55_+niDm=Gu10WDCkyYmLOsaezg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 27, 2024 at 8:45 PM AbdelAziz Sharaf
<mickelpower75(at)gmail(dot)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 possible issues 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 request is 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-11-28 11:11:05 Re: tab_complete for copy(merge
Previous Message Amit Kapila 2024-11-28 11:07:59 Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY