You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: