Opened 16 years ago
Closed 16 years ago
#7384 closed (invalid)
database introspection on oracle is broken
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 0.96 |
| Severity: | Keywords: | oracle introspection | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The db/backends/oracle/introspection.py module is just plain useless in Django-0.96.2
The attached patch is at least much closer...
Attachments (3)
Change History (4)
by , 16 years ago
| Attachment: | oracle_intro.patch added |
|---|
by , 16 years ago
| Attachment: | introspection.py added |
|---|
by , 16 years ago
| Attachment: | introspection_without_debug.py added |
|---|
comment:1 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
There's been a large amount of work on Oracle support since the 0.96 release; please try with Django trunk to see if the problem persists, and search for existing tickets to see if any remaining issues have already been reported.