2.0.x new way to deal with schema breaks multi-schema apps

[kaligrafy]

I have a rails app that uses multiple schemas: schema_search_path: "rails, datawarehouse, public"

I want postgis to use the public schema. With versions 1.x of activerecord-postgis-adapter, it worked well (postgis went to the public schema, and all my other tables were sent to rails or datawarehouse schemas according to a parameter in my migrations files.

Now, with version 2.0.x, only the public schema is created and the other two are ignored (not created), so all my tables go to the public schema when migrating.

[teeparham]

Thanks for reporting this issue. Can you write a failing test for this scenario? See https://github.com/rgeo/activerecord-postgis-adapter/blob/master/test/tasks_test.rb

For reference, I suspect PR #114 caused the change.

[teeparham]

This adapter should now use the default postgresql adapter from rails to do the schema and structure dumps. It sounds like you want the schema dump to include the 'rails' or 'datawarehouse' schemas in the export. I'm not sure why that would not be happening without more knowledge about your setup.

This might help: http://timnew.github.io/blog/2012/07/17/use-postgres-multiple-schema-database-in-rails/

[teeparham]

Closing as stale. Please re-open if this is still an issue.