Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial data fixtures and FastFixtureTestCase #138

Open
SoftwareMaven opened this issue Aug 29, 2013 · 1 comment
Open

Initial data fixtures and FastFixtureTestCase #138

SoftwareMaven opened this issue Aug 29, 2013 · 1 comment

Comments

@SoftwareMaven
Copy link

If I have some initial data in a fixture, when I use FastFixtureTestCase, I wind up with conflicting primary keys. It looks like somewhere the auto-increment for the primary key gets reset. Since the initial data fixture has used a number, at some point, they clash and my test fails.

This initial data is not used as part of the tests; rather, it is initial data that the system needs for basic deployment. Any ideas how I can maintain use of FastFixtureTestCase while not blowing up?

I should mention I am using South as well.

@jwhitlock
Copy link
Contributor

Does this still happen with nose 1.4 and a current Django version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants