queryInterface.addColumns always adds "public." to the table name for Postgres

Not sure if I’m doing anything wrong, but this is a pretty big blocker for me right now. I need to add a column to an existing table which is in a schema different from “public”.

Simply using the table name throws this error: "relation \"public.mytable\" does not exist"

Adding the schema to the table name throws (this works for addIndex): "relation \"public.default.mytable\" does not exist"

I’ve tried adding a schema property to the options object, like for the createTable method, but it seems to be ignored.

Is there a way to avoid “public” always getting added? I’ve also haven’t seen a way to send arbitrary sql statements to the queryInterface, this way I could just send the “alter table” myself.

sequelize version: 5.19.4

[allenwu1973]

For those who are like me found this from google search, this is duplicate of #11742

It seems like there’s no way to specify a default schema for migrations (won’t work with addColumn), you can however, change all your migrations to specify schema instead

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the “stale” label. 🙂