Opened 16 years ago
Closed 13 years ago
#10837 closed Cleanup/optimization (fixed)
postgresql missing field type codes in data_types_reverse
| Reported by: | trbs | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | bpchar, data_types_reverse, introspection inspectdb |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I've created a patch to add 'char' field support to data_types_reverse in the PostgreSQL.
As a char(50) is basically the same (CharField) as a varchar(50) for Django.
Also created a second patch which also adds 'int8' to the list as an 'IntegerField'.
This would make inspectdb and other (third-party code?) that uses data_type_reverse a bit more complete for PG.
Attachments (3)
Change History (10)
by , 16 years ago
| Attachment: | 10837-bpchar.diff added |
|---|
by , 16 years ago
| Attachment: | 10837-bpchar-int8.diff added |
|---|
comment:1 by , 15 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 15 years ago
comment:3 by , 14 years ago
| Severity: | → Normal |
|---|---|
| Type: | → Cleanup/optimization |
comment:4 by , 14 years ago
| Easy pickings: | unset |
|---|---|
| Patch needs improvement: | set |
10837-bpchar-int8.diff fails to apply cleanly on to trunk
comment:5 by , 13 years ago
| Keywords: | inspectdb added |
|---|---|
| UI/UX: | unset |
comment:6 by , 13 years ago
| Patch needs improvement: | unset |
|---|---|
| Version: | 1.0 → SVN |
20/int8 is now present in Django code.
Note:
See TracTickets
for help on using tickets.
Alex do you want to apply the patch like it is, Or should we broaden this ticket to make the (reversed) type list as complete as possible ?