dropTable not schema-aware?

So, you can createTable in a schema, it creates the table in the assigned schema, but seems like we are not able to dropTable on the down migration when reversing changes?

When using this migration:

return queryInterface.dropTable('ivr', {
      schema: 'raw_filemaker'
    });

gives DROP TABLE IF EXISTS "ivr";

This is in v3.6.0 w/postgresql.

Upon superficial scan, seems like return Utils._.template(query)(values).trim() + ';'; in createTableQuery properly prepends the schema, whereas return Utils._.template(query)({...}); at the end of dropTableQuery does not. Oddly, they both call this.quoteTable(tableName)?

[alexmon]

@paulxtiseo @mickhansen is right, try :

return queryInterface.dropTable( { tableName: ‘ivr’, schema: ‘raw_filemaker’
} );

it worked for me

[v1d3rm3]

I think it will be better if the options of dropTable are consistent with createTable, so you could define schemas in dropTablelike in createTable. I think it’s a security issue.