Migrations + PostGIS

Describe the bug Migrations does not recognize the tables under the “topology” schema/tablespace as “system tables”, attempting to remove them. They seem to be treated as tables within the same context/tablespace.

Migration excerpt:

    this.addSql('drop table if exists "layer" cascade;');
    this.addSql('drop table if exists "topology" cascade;');

If I create an entity names “Layer”, the migration attempts to modify the existing “layer” table as if it belonged to the same tablespace.

Additional context https://github.com/wkrueger/geostore

[corbt]

Ah I see, being able to migrate diffs across all the schemas could be a handy feature I guess!

Building in support for an ignoreSchema configuration option would be nice, but since PostGIS is so widely used I think including its schemas by default would be a good start. Those schemas are named tiger and topology. I’ll open a PR.

[mnowaczyk]

It’s still broken, this time not with PostGIS, but with pg_cron. Generated migrations try to drop schema “cron”, even though it’s not in the search path. In my opinion the ORM shouldn’t touch other schemas unless instructed to do so.