#34376: Admin has no support for unique constraint fields (while using SQLite?)
-------------------------------------+-------------------------------------
Reporter: Alex | Owner: nobody
Urbanowicz |
Type: | Status: new
Uncategorized |
Component: | Version: 4.1
contrib.admin |
Severity: Normal | Keywords: sqlite unique admin
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The context is an Admin based application - all database operations are
done using Admin. The backend is SQLite.
One of the fields in the application is a field for an (unique) ip
address:
`ip = models.GenericIPAddressField(protocol='IPv4', unique=True)`
When there's an append to enter duplicate IP address, the application
crashes to a 500 error:
`django.db.utils.IntegrityError: UNIQUE constraint failed: <table>.ip`
Attempt at handling that error by catching the exception and emitting an
message leads to another error:
`django.db.transaction.TransactionManagementError: An error occurred
in the current transaction. You can't execute queries until the end of the
'atomic' block.`
I would expect that, since the ORM supports unique fields, there's some
Admin UI to handle constraint errors in a similar way to validation
errors, and not fall flat and give the user a 500 error.
--
Ticket URL: <https://code.djangoproject.com/ticket/34376>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701869d77c46a-878b2b54-51f2-4f81-a5b9-4bf83a227dea-000000%40eu-central-1.amazonses.com.
