Skip to content

Caching empty querysets breaks get_or_create #32

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.

Sign up for GitHub

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

Jump to bottom
Open
pmclanahan opened this issue Sep 25, 2012 · 0 comments
Open

Caching empty querysets breaks get_or_create #32

pmclanahan opened this issue Sep 25, 2012 · 0 comments
Labels
bug

Comments

@pmclanahan
Copy link

When empty queryset caching is enabled, get_or_create seems to always force creation causing multiple calls to produce IntegrityErrors for existing primary keys. I'll see what I can do about writing a test to prove this, but this is what I'm seeing in my app's tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pmclanahan @tobiasmcnulty