This project is archived and is in readonly mode.
[patch] schema path in postgresql is broken
Reported by Daniel Schreiber | January 7th, 2010 @ 03:17 PM
How to reproduce:
* Create a DB with multiple schemas. * create tables/views/... in
multiple schemas * configure rails to know some schemas in
config/database.yml * run rake db:test:prepare
What happens:
* unpatched rails calls pg_dump with the wrong options -> fail *
unpatched rails adds insert statements for the schem_migrations
table without resetting the schema search_path in the dumpfile
Comments and changes to this ticket
-
Julian Mehnle April 6th, 2010 @ 12:10 AM
I think this is a duplicate of #2695, which has been resolved.
-
Santiago Pastorino February 2nd, 2011 @ 04:44 PM
- State changed from “new” to “open”
- Tag changed from “2.x, patch” to “2x, patch”
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 04:44 PM
- State changed from “open” to “stale”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Daniel Schreiber