-
-
Notifications
You must be signed in to change notification settings - Fork 339
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
Django 4.1 unique constraint failing #594
Labels
Comments
I also experience the same issue - constraints are causing the exceptions. It looks like the query issued by them is not linked to any model. |
SebCorbin
added a commit
that referenced
this issue
Oct 28, 2022
albertyw
pushed a commit
that referenced
this issue
Oct 29, 2022
I see some commits here. When will a new version be released? |
Pending #622 |
#439 is older than 2 years. Do you really want to postpone a release because of it? |
No, I don't. I think we should do a release asap. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently we've upgraded our project to Django 4.1 (and Silk to 5.0.1 from 4.3.0), and a unique constraint on a model has begun to fail whilst Silk is enabled.
The error is being raised here: silk/sql.py:94
Full stack trace:
And finally, the query attempted to be run:
Prior to the Django 4.1 upgrade, this constraint was working without a hitch with Silk running.
All other unique constraints within the system appear to still be functioning fine, including two other unique constraints on this same model, but this one with
condition=~Q()
is failing.The text was updated successfully, but these errors were encountered: