Opened 18 years ago
Closed 18 years ago
#3775 closed (fixed)
mysql_old backend use mysql backend
Reported by: | anonymous | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | django-admin.py inspectdb | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
Attachments (1)
Change History (5)
by , 18 years ago
Attachment: | mysql_old_patch.patch added |
---|
comment:1 by , 18 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 18 years ago
I underestand that mysql_old is compatible support for people who can't upgrade MySQLdb immediately. Without this patch I can't use django with mysql with older version than MySQLdb-1.2.1p2.
If I try to use mysql_old and run python manage.py syncdb
it will raise ImportError "MySQLdb-1.2.1p2 or newer is required;".
Problem is mysql_old 'introspection.py' imports from django.db.backends.mysql.base import quote_name
not from django.db.backends.mysql_old.base import quote_name
file.
comment:3 by , 18 years ago
Component: | Database wrapper → django-admin.py inspectdb |
---|---|
Has patch: | set |
Patch needs improvement: | set |
Resolution: | invalid |
Status: | closed → reopened |
Triage Stage: | Unreviewed → Accepted |
Ah ... and the patch is for the directory django/db/backends/mysql_old! That makes sense, but it wasn't at all obvious.
Please provide a little bit more background when you write a ticket. As we don't see
what you're doing, it's sometimes hard to understand. Also, patches should contain
the full path from the django source directory, so there's no doubt about which directory
you mean.
I checked 'patch needs improvement' since the patch should really have the full path before
core developers deal with it.
Can you provide more info about this? why is this needed? what does it do?