Re: Database migrations

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Saturday, March 13th, 2021 at 22:04, Alejandro Román <alejandro(at)aroman(dot)sh> wrote:

> Hello,
>
> > 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?
>
> It does. Actually, there is a known JS library that does exactly that: Knex.js (1). It allows you to define your SQL in plain JS (e.g. `knex.schema.createTable(‘users’, …)`). It will then keep track of which migrations (JS files) have been ran and which need to be run. It stores this metadata in a table called “migrations” (you can configure the exact name).
>
> (1) http://knexjs.org/#Migrations
>
> Best wishes,
>
> Alejandro

Hi Alejandro,

Thank you for the information. I'll read through the documentation for that as well. Having everything in JavaScript would be quite helpful in the long run I think but I do like the idea of extensions as well. I'll do some testing and see which option works out best.

Simon.