Feature: Migrations

Just like replace is doing it for Data, we could add an utility function which looks at first if a table exists, if not create it, and if the table exists also checks if fields|columns are missing, adds them in a non-destructive fashion.

I’ve already made an Table Creator that i could PR(if wanted)

Ex.:

checkTableExists('session').then(...).catch(() => {
           createTable("session", [
                new BaseField('id').isUnique().setType("VARCHAR(256)"),
                new BaseField('created_at').setType('BIGNUMBER')
            ])
        })

It doesn’t yet support checking for fields missing. Though creating a table would be a useful addition i think.

[rahmanfadhil]

Awesome! I’m very glad you like it!

We should take another look at some of the functions and let them throw if default case happens:

That’s a pretty easy thing to fix. And the tests will fail anyway since we have a special test case for this. So, everything is good.

https://github.com/rahmanfadhil/cotton/blob/5828520c05d5fe4edbe717cceca3e4df4f82f174/src/migrations/migration_test.ts#L5-L13

Maybe later we could even make an SQL Exporter/Importer(that would be useful for the moment a project wants to branch out to a bigger type of database sqlite => mysqldb or mariadb), i think i got something like that already somewhere for JS.

I’m not sure if anyone needs to export/import their database programmatically. Maybe we can provide a CLI for it? 🤔

Anyway, I’m really excited to have some kind of database seeder and factory to populate the database with realistic dummy data for development and testing purposes.

Lastly, I’m going to remove the old migration code in src/table.ts, because everything is already moved to src/migrations.

I will keep this issue open until this feature is released and merged into the master branch. So, if you have any ideas or suggestions, I’m more than happy to discuss about it. Thanks!

[rahmanfadhil]

This feature is now merged with master 🎉

Checkout the docs for more info.