#321 closed defect (fixed)
Revision 494 breaks MySQL
| Reported by: | anonymous | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | |
| Severity: | blocker | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Immediately after upgrading to [494], the MySQL backend has stopped functioning. Django reports the following error:
ImproperlyConfigured: Could not load database backend: cannot import name CursorNW. Is your DATABASE_ENGINE setting (currently, 'mysql') spelled correctly? Available options are: 'mysql', 'postgresql', 'sqlite3'
Note:
See TracTickets
for help on using tickets.
What version of MySQLdb are you using?
Try this in the Python interactive prompt:
It appears you're using a version of MySQLdb that doesn't support
CursorNW. I'm using 0.9.2, and it works here.