Wrench only supports GOOGLESQL dialect today. It fails during schema migration table creation because postgres doesn't support that syntax. It's also possible that use of memefish may cause issues (e.g. comment removal), but I haven't see issues with that in practice. You can workaround this by just precreating the migration table in a postgres-compliant way.
Can I put up a PR to detect the dialect via API (but can force dialect with flag) and use a compliant CREATE TABLE statement?
Wrench only supports GOOGLESQL dialect today. It fails during schema migration table creation because postgres doesn't support that syntax. It's also possible that use of memefish may cause issues (e.g. comment removal), but I haven't see issues with that in practice. You can workaround this by just precreating the migration table in a postgres-compliant way.
Can I put up a PR to detect the dialect via API (but can force dialect with flag) and use a compliant CREATE TABLE statement?