This project is archived and is in readonly mode.
Unable to use fixtures for testing models that make use of the postgres schema construct
Reported by Sam Meder | February 26th, 2010 @ 12:21 AM
This problem seems to exist in both rails 2.3.5 and 3.0.0beta.
I am working on a app where I would really like to make use of some form of namespace construct in my database schema. Since we're working with postgres (8.4) this happens to be the 'schema' construct.
To test that this is feasible, I created a custom migration to set up the schema followed by a customized model driven migration. So far, so good. Next I moved the the auto generated fixture file to ..yml and wrote a simple unit test for one of the validations associated with the model.
Now, when I try running the unit test with rake test:units the process fails in the setup phase. In particular, the call to connection.reset_pk_sequence! from Fixtures.create_fixtures(...) fails since the sequence relation discovered by connection.pk_and_sequence_for(table) is not schema (namespace) qualified.
I've attached a patch to the postgresql adapter that fixes this issue for me, but I am uncertain if it is generic enough to work with other versions of postgres.
Comments and changes to this ticket
-
Sam Meder April 11th, 2010 @ 05:39 AM
- Assigned user cleared.
-
Santiago Pastorino February 2nd, 2011 @ 04:59 PM
- State changed from new to open
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:59 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>