MIME-Version: 1.0
From: AbdelAziz Sharaf <mickelpower75@gmail.com>
Date: Fri, 22 Nov 2024 14:30:32 +0200
Message-ID: <CAObAeFim3uYus8EEFZ_dC7iLsJ6BDkUH-Pu-DTyjvuk28roGxQ@mail.gmail.com>
Subject: [Feature Request] Schema Aliases and Versioned Schemas
To: pgsql-hackers@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000002c4dd606277f8d3f"
Archived-At: <https://www.postgresql.org/message-id/CAObAeFim3uYus8EEFZ_dC7iLsJ6BDkUH-Pu-DTyjvuk28roGxQ%40mail.gmail.com>
Precedence: bulk

--0000000000002c4dd606277f8d3f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dear PostgreSQL Development Team,

I=E2=80=99d 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

**Benefits:**
- migration process for under dev projects will be more easier
- App env stability, where no data need to be changed in the app other than
the logic of newly modified schema, not the connection nor the schema or db
name
- no need for external tools or servers to migrate or rollback
- minimal downtime between migrations and rollback

**why I post here**
it's addition to core pgsql
>> if it's not the right place : I could contact the mailing list you know
it's supposed to take feature requests

Thank you for considering this feature request.
I look forward to feedback or further discussion on this idea.

Best regards,
Abdelaziz sharaf

--0000000000002c4dd606277f8d3f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear PostgreSQL Development Team,<br><br>I=E2=80=99d like =
to propose a new feature for consideration: schema aliases and versions<br>=
<br>**Problem Statement:**<br>For migrating=C2=A0old db to new one, one mus=
t use an external tool or define a dedicated migration=C2=A0script where al=
l possible issues could arise<br><br>**Proposed Solution:**<br>there is two=
 ways I may think about<div>- versioned schemas : where=C2=A0every version =
act as a separate schema and the `latest` one or the one the program reques=
t is the one in use and each new schema could inherit a table, index, view,=
 ... without additional data<br>- aliases : where every new schema is defin=
ed and migrated=C2=A0separately then an alias=C2=A0is set for the one in us=
e<br><br>**Benefits:**<br>- migration process for under dev projects will b=
e more easier</div><div>- App env stability, where no data need to be chang=
ed in the app other than the logic of newly modified schema, not the connec=
tion nor the schema or db name</div><div>- no need for external tools or se=
rvers to migrate or rollback</div><div>- minimal downtime between migration=
s and rollback<br><br>**why I post here**<br>it&#39;s addition to core pgsq=
l<br>&gt;&gt; if it&#39;s not the right place : I could contact the mailing=
 list you know it&#39;s supposed to take feature requests<br><br>Thank you =
for considering this feature request.</div><div>I look forward to feedback =
or further discussion on this idea.<br><br>Best regards,<br>Abdelaziz shara=
f<br></div></div>

--0000000000002c4dd606277f8d3f--