#28116: Filtering PostgreSQL exception based on message is too brittle
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: felixxm
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"e776dd2db677d58dcb50aea20d3bb191537df25b" e776dd2d]:
{{{
#!CommitTicketReference repository=""
revision="e776dd2db677d58dcb50aea20d3bb191537df25b"
Fixed #28116 -- Used error code filtering in PostgreSQL test database
creation.
Thanks Claude Paroz and Tim Graham for reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28116#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.93aa49505afc38e7234e9a3a111955fc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
