Open
Conversation
Since ActiveRecord 3.2.14, db/structure.sql automatically includes a "SET search_path TO" statement before adding the "INSERT INTO schema_migrations" statements, which is handy. However, if you haven't set schema_search_path in your config/database.yml (I deliberately haven't) and you use multi_schema in your migrations then the search path will flip-flop between "$user",public and public depending on whether you've run "rake db:structure:dump" or "rake db:migrate". This makes version control tedious. The default client search path of "$user",public can be overridden in postgresql.conf so I have made this configurable through MultiSchema.default_search_path as part of this fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since ActiveRecord 3.2.14, db/structure.sql automatically includes a "SET search_path TO" statement before adding the "INSERT INTO schema_migrations" statements, which is handy.
However, if you haven't set schema_search_path in your config/database.yml (I deliberately haven't) and you use multi_schema in your migrations then the search path will flip-flop between "$user",public and public depending on whether you've run "rake db:structure:dump" or "rake db:migrate". This makes version control tedious.
The default client search path of "$user",public can be overridden in postgresql.conf so I have made this configurable through MultiSchema.default_search_path as part of this fix.