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)

introspection.py.diff (966 bytes ) - added by pyrou 14 years ago.

Download all attachments as: .zip

Change History (9)

by pyrou, 14 years ago

Attachment: introspection.py.diff added

comment:1 by Ramiro Morales, 14 years ago

Triage Stage: UnreviewedAccepted

See also #14266.

comment:2 by Adam Nelson, 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 Gabriel Hurley, 14 years ago

Component: django-admin.py inspectdbCore (Management commands)

comment:4 by patchhammer, 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 Julien Phalip, 13 years ago

Type: UncategorizedBug

comment:6 by Ramiro Morales, 13 years ago

Keywords: inspectdb added
UI/UX: unset

comment:7 by Jacob, 13 years ago

milestone: 1.3

Milestone 1.3 deleted

comment:8 by Ramiro Morales, 13 years ago

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.
Back to Top