Date: Sat, 13 Mar 2021 21:40:27 +0000
To: "pgsql-novice@lists.postgresql.org" <pgsql-novice@lists.postgresql.org>
From: Simon Connah <simon.n.connah@protonmail.com>
Reply-To: Simon Connah <simon.n.connah@protonmail.com>
Subject: Database migrations
Message-ID: 
 <DZDT1SCFF7_nJRcZylu8tod4dlTmOX1hAuAlselavvkA4HJAFbOUPC_33W7IxDtMdbzQBPYGPN6p0N58SRHjP3D-JuI8CEyRn3xL1VF4t30=@protonmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/DZDT1SCFF7_nJRcZylu8tod4dlTmOX1hAuAlselavvkA4HJAFbOUPC_33W7IxDtMdbzQBPYGPN6p0N58SRHjP3D-JuI8CEyRn3xL1VF4t30%3D%40protonmail.com>
Precedence: bulk

Hi,

I'm sorry if this is a rather stupid question but I'm fairly new to databas=
es and was wondering if anyone could offer some advice?

I have an app I am developing using Node.js and PostgreSQL 13.2. I have the=
 basic tables I want to start with but I know that as development progresse=
s change is going to be required. Since this is an open-source project peop=
le are going to want to upgrade from one version to the next and that might=
 require changes to the database structure. What is the best way to handle =
this?

I was thinking about just having a bunch of SQL files with a version number=
 and date and applying them to the database from oldest to newest (with a t=
able storing information for files that have already been processed). Does =
this sound like a reasonable solution?

If not could someone point me in the right direction, please?

Thank you for your help.

Simon.