#15782: Runserver/runfcgi/startup with MySQL is unlike any other database
-------------------------------------+-------------------------------------
Reporter: toofishes | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Database layer
Version: 1.3 | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords:
Needs documentation: 0 | Has patch: 1
Patch needs improvement: 0 | Needs tests: 0
| Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by toofishes):
* has_patch: 0 => 1
Comment:
Since it wasn't clear whether you thought option 1, 2, 3, or none of the
above was the best way to resolve this, I'll propose this patch which
basically implements suggestion #2. If we can get a connection, we will
continue to check the < 5.0.3 bits; else we will just skip it, do what we
can without a connection, and make sure we start up. The first page you
hit will then show a 500 error saying the DB connection could not be
established, but one will not have to restart Django once the DB comes up.
--
Ticket URL: <http://code.djangoproject.com/ticket/15782#comment:3>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
