pgroll
pgroll copied to clipboard
xataio
PostgreSQL zero-downtime migrations made easy
Drop index has trouble with case sensitive names: ``` [{ "drop_index": { "name": "idx_AREA_CODE" } } ] ``` > migration is invalid: index "idx_AREA_CODE" does not exist It requires escaped...
Ensure that 'alter column' operations that rename a column and also specify `down` SQL (such as those that alter some other column attribute at the time of the rename) must...
Will there be support for migrating triggers? Also, can pre-existing or new triggers interfere at all with the migration process?
When a column is renamed and modified in some other way that requires an `up` and `down` SQL (eg changing its type), migration authors should be able to refer to...
```json { "name": "1_initial_schema", "operations": [ { "create_table": { "columns": [ { "name": "id", "nullable": false, "pk": true, "type": "uuid", "unique": true } ], "name": "lang" } }, { "create_table":...
Coming from the traditional style of migration tools that you're probably familiar with, I've grown accustom to tooling that provides a clear path from an empty database, to one that...
Hi there! I'm really interested in using this tool, however as a user of SQLc, I require the schema to be available as SQL. Is there any plan to support...
Hello, I really appreciate how well ```pgroll``` works with JSON files. It would be even more convenient if there was an option to specify an SQL file for migration. For...
Alter column operations should support specifying fields that are unchanged as no-ops. For example, this migration: ```json { "name": "35_alter_column_multiple", "operations": [ { "alter_column": { "table": "events", "column": "name", "name":...
TODO list: - [x] Apply max length validation for temporary name - [x] Operations validation - [x] Schema name validation - [x] triggers name validation fixes: https://github.com/xataio/pgroll/issues/64
