#90 closed enhancement (fixed)
Add "django-admin.py inspectdb" option
Reported by: | Adrian Holovaty | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | Tools | Version: | |
Severity: | normal | Keywords: | |
Cc: | miernik@… | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
django-admin.py inspectdb
would take an argument -- the database name -- and would introspect the existing database-table structures and print a Django model to standard output.
Change History (7)
comment:1 by , 19 years ago
Description: | modified (diff) |
---|
comment:2 by , 19 years ago
milestone: | → Version 1.0 |
---|
comment:3 by , 19 years ago
Status: | new → assigned |
---|
comment:4 by , 19 years ago
comment:5 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
As of [398], I'm closing this, because it's good enough at this point to be used in common cases. I'll be filing lower-priority tickets for individual features we need to add to inspectdb
, but for version 1.0, this will suffice.
comment:6 by , 19 years ago
Cc: | added |
---|
Note:
See TracTickets
for help on using tickets.
(In [384]) Added first stab at 'django-admin.py inspectdb', which takes a database name and introspects the tables, outputting a Django model. Works in PostgreSQL and MySQL. It's missing some niceties at the moment, such as detection of primary-keys and relationships, but it works. Refs #90.