Code

Opened 4 years ago

Closed 2 years ago

#14618 closed Bug (wontfix)

unable to "inspectdb" on mysql4 database

Reported by: pyrou Owned by: nobody
Component: Core (Management commands) Version: master
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 4 years ago.

Download all attachments as: .zip

Change History (9)

Changed 4 years ago by pyrou

comment:1 Changed 4 years ago by ramiro

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

See also #14266.

comment:2 Changed 4 years ago by adamnelson

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 Changed 3 years ago by gabrielhurley

  • Component changed from django-admin.py inspectdb to Core (Management commands)

comment:4 Changed 3 years ago by patchhammer

  • Easy pickings unset
  • Patch needs improvement set
  • Severity set to Normal
  • Type set to Uncategorized

introspection.py.diff fails to apply cleanly on to trunk

comment:5 Changed 3 years ago by julien

  • Type changed from Uncategorized to Bug

comment:6 Changed 3 years ago by ramiro

  • Keywords inspectdb added
  • UI/UX unset

comment:7 Changed 3 years ago by jacob

  • milestone 1.3 deleted

Milestone 1.3 deleted

comment:8 Changed 2 years ago by ramiro

  • Resolution set to wontfix
  • Status changed from new to closed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.