Opened 10 years ago
Closed 10 years ago
#23385 closed Bug (needsinfo)
inspectdb on Oracle: interpretation of NUMBER(1,0) cols as boolean
| Reported by: | Agos | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | 1.7-rc-3 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
While NUMBER(1,0) is often used to used to represent booleans, but this is not always the case; there should be a way to avoid this ambiguity.
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Do you have a suggestion to address this? I don't see it as an issue as
inspectdbdoesn't claim to provide definitive model generation and you can easily edit the fields afterward to suite your needs.