#29015: Add an error when the PostgreSQL database name length limit is exceeded
-------------------------------------+-------------------------------------
Reporter: Tadej Janež | Owner: Priyansh
Type: | Saxena
Cleanup/optimization | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"6b3d2920438746d260f7d158a91db53450055ae2" 6b3d2920]:
{{{
#!CommitTicketReference repository=""
revision="6b3d2920438746d260f7d158a91db53450055ae2"
Fixed #29015 -- Added an exception if the PostgreSQL database name is too
long.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29015#comment:5>
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/064.60d3815e793ce70211cbb93bf2b0a15c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
