Data in enum tables should be tracked in console-generated migrations #2817
Description
Version: Beta.6
Image: Docker CLI Migrations
Platform: K8s
Host: macOS Mojave
The new Enum table seems it requires at least one row - to be able to be connected foreign key constraint. It breaks migrations as well.
Here is an excerpt from the logs:
...
...
...
level=fatal msg="apply failed: [constraint-violation] the table \"my_enum_table\"
cannot be used as an enum because the table must have at least one row
($.args[6].args)\r\nFile:
'1567433643579_alter_table_public_my_enum_table_set_enum_true.up.yaml
...
...
...
Thanks!