Opened 14 years ago
Closed 13 years ago
#14618 closed Bug (wontfix)
unable to "inspectdb" on mysql4 database
Reported by: | pyrou | Owned by: | nobody |
---|---|---|---|
Component: | Core (Management commands) | Version: | dev |
Severity: | Normal | Keywords: | inspectdb |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
I tried an inspectdb on a mysql 4 database, and got an Exception
django.db.utils.DatabaseError: (1146, "Table 'information_schema.key_column_usage' doesn't exist")
raised from here : browser/django/trunk/django/db/backends/mysql/introspection.py
of course, that's because I'm on mysql 4
adding DatabaseError
on the list of expected Error fix the problem
Attachments (1)
Change History (9)
by , 14 years ago
Attachment: | introspection.py.diff added |
---|
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 14 years ago
The patch looks fine and simple. Can you confirm that you're on MySQL 4.1 vs 4.0? I think this would be a problem on 4.1 (because there's no information_schema), but I want to confirm exactly what version you're on.
comment:3 by , 14 years ago
Component: | django-admin.py inspectdb → Core (Management commands) |
---|
comment:4 by , 14 years ago
Easy pickings: | unset |
---|---|
Patch needs improvement: | set |
Severity: | → Normal |
Type: | → Uncategorized |
introspection.py.diff fails to apply cleanly on to trunk
comment:5 by , 13 years ago
Type: | Uncategorized → Bug |
---|
comment:6 by , 13 years ago
Keywords: | inspectdb added |
---|---|
UI/UX: | unset |
comment:8 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
See also #14266.