Commit Graph

7 Commits

Author SHA1 Message Date
Charles Brandt
0d3e925f27
Fix #1290 issue running migrations (#1585)
# Description

In issue #1290 folks report difficulty running migrations on an existing
instance. The current migration table includes a `name` column, but no
`id` column:

```
CREATE TABLE IF NOT EXISTS migrations (
  name VARCHAR(255)  PRIMARY KEY,
  executed_at TIMESTAMPTZ DEFAULT current_timestamp
);
```

By changing the `migrations.sh` script to use the `name` field, the
migrations run as expected.

## Checklist before requesting a review

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my code
2023-11-04 21:30:03 +01:00
João Victor Sezanosky Dalla Valle
ae7a8ea5ea
fix(docs): add prerequisites section in step 2 (#1149)
* docs: Add prerequisites section in step 2

* feat: showing errors

* docs: specifying the prerequisites directly, stating that it is not necessary to perform further steps

---------

Co-authored-by: Zineb El Bachiri <100568984+gozineb@users.noreply.github.com>
2023-09-27 09:28:59 +02:00
Ryder Wishart
76d409fbec
If .migration_info values are missing, prompt user for them (#637) 2023-07-13 18:57:50 +02:00
escoolioinglesias
f2a06dc6de
fixed gum flag (#567) 2023-07-09 22:45:40 +02:00
Stan Girard
f0a30b8452 docs(migration): updated table 2023-07-03 14:41:33 +02:00
Stan Girard
17d4d49cd9
Docs/testing strategy (#465)
* docs(tests): testing strategies

* fix(migration): migration id to name
2023-07-03 11:40:19 +02:00
Stan Girard
76156fdad3 feat: 🎸 migration
added migration script
2023-07-03 11:11:29 +02:00