Open maxcan opened 4 years ago
@maxcan We're aware of the issue and some discussions are going on at https://github.com/hasura/graphql-engine/issues/2817
Closing this issue in favour of the other one.
@tirumaraiselvan thanks for the update. looking forward to 1.4!
Is this fixed in 2.0.0 ?
Please can this be added to 2.0.0 milestone. Still not supported. 🙏
If you use that approach to squash migrations, you lose any manual
INSERT INTO
SQL migrations that you've run.The main problem with this is that if you have any enum tables, they new migrations will break since enum tables must have at least one row.
At a minimum, this should be noted in the docs (happy to put in some copy if you want) but ideally the
--from-server
option should have an option to include manual SQL insertion migrations or a big flashing warning when you try to run it on a DB with enum tables.This is on GQL Engine 1.1 but has been an issue since enum tables were released.