igorkamyshev/trona

Write DB migrations with SQL and run them with a CLI

Who I am 👨‍💻

Hi, I am Igor — a software engineer at Aviasales working on web platform to support product teams sustainability.

My areas of interest

• Effector — business logic with ease

Get in touch

• Email: [email protected]
• Telegram: https://t.me/igorkamyshev

trona's Issues

JS-api

Check down script

Add option for rerun scripts for test down script. Like "up-down-up" in transactions.

Examples for SQLite, PG, MySQL

Add examples for popular SQL Databases to README

Bug with alter type

Minimize logs with `-s, --silent` option

We should not write so many logs with this option

Unify all scripts under single console command

Now we use trona-evolutions-init and trona-evolutions-run and it looks terrible.

Expected behaviour:

• trona-evolutions init for prepare DB for trona
• trona-evolutions run for run evolutions

Dry run

Add option for dry run.

JSON output option

Allow to add custom names of evolutions

Like 1-init.sql, 2-add-user.sql, etc.

Dependabot can't resolve your JavaScript dependency files

Dependabot can't resolve your JavaScript dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Error whilst updating eslint in /yarn.lock:
Couldn't find package "@commitlint/ensure@^8.3.4" required by "@commitlint/rules@^8.3.4" on the "npm" registry.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Add multiple config support

This may be needed for multiple databases in the same project

Add --help flag

Confirmations

Now, trona execute command immediately after user type it into terminal. We need confirmation for any command.

Add transactions

Nice evolution you have here. It would be a shame if first half of your evolve script will run successfully and second will fail, making your db's state inconsistent

Tests

This project has no tests. It's not right way! We need some unit tests for that.

Linting

Code-styles in solid-soda projects are different. We need setup linting for this project.

Update README with all options

Some options are not described in README (e.g. -c, -d). Need to add this info to readme.

Clean up docs

Docs are too complex. We ought to simplify it.

Add degrade script and update-only script

Now, trona able execute up script. But, in some cases down script must be executed.

Expected behaviour:

• evolutions abort for aborting last evolution
• evolutions abort {{n}} for aborting last n evolutions

Remove --init flag

I guess, we must remove --init flag, and just init all tables on first run.

Dependabot couldn't authenticate with registry.npmjs.org

Dependabot couldn't authenticate with registry.npmjs.org.

You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.

View the update logs.

Add a good mistake resolution guide

If user makes some mistakes in his evolutions it could lead to inconsistent db state (e.g. invalid degrade script) in this case he need to fix his db state manually. We should have section about this in readme.

Also we should have a script which can forcibly update an evolution record (In case of situation from above happens) and user is too afraid to go to DB or mistake is relatively minor (e.g. broken DOWN script)