Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#321 closed defect (fixed)

Revision 494 breaks MySQL

Reported by: anonymous Owned by: adrian
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: UI/UX:

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'

Change History (2)

comment:1 Changed 10 years ago by adrian

  • Status changed from new to assigned

What version of MySQLdb are you using?

Try this in the Python interactive prompt:

from MySQLdb.cursors import CursorNW

It appears you're using a version of MySQLdb that doesn't support CursorNW. I'm using 0.9.2, and it works here.

comment:2 Changed 10 years ago by adrian

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [495]) Fixed #321 -- Undid [494], which assumed the installed version of MySQLdb had a 'cursors.CursorNW'. Thanks for being consistent, MySQLdb. This opens #316 again.

Note: See TracTickets for help on using tickets.
Back to Top