Re: Database migrations

Hi Simon,

Another option (and the one we use) is a tool called flyway -
https://flywaydb.org/. There is a free community edition, and it is pretty
comprehensive. There are docker images you can use during ci.

Flyway supports versioned (run once) migrations, repeatable (run when
changed) migrations, and a bunch more.

Other than being a user of the community edition, I have no association
with flyway.

Cheers,

Steve

On Sun, Mar 14, 2021 at 8:40 AM Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com>
wrote:

> Hi,
>
> I'm sorry if this is a rather stupid question but I'm fairly new to
> databases 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
> progresses change is going to be required. Since this is an open-source
> project people 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 table 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.
>
>
>
>
>