Opened 6 years ago
Last modified 6 years ago
#30346 closed Bug
InspectDB doesn't test for UUID (at least) on PostgreSQL — at Initial Version
Reported by: | Gui Pedreira | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 2.2 |
Severity: | Normal | Keywords: | inspectdb, postgresql, uuid |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I was trying to do some reverse stuff...
Importing models from a "Legacy" Database,
as it turns out, inspectdb doesn't seem to go nicely with UUIDs,
At least on PostgreSQL.
\d resource ------------+--------------------------+-----------+----------+--------- id | uuid | | not null | name | character varying(255) | | not null | code | character varying(255) | | not null |
I've tried adding djago.contrib.postgres to installed apps, without luck.
Am I missing something? Already tried --include-views and --include-partitions too.
Note:
See TracTickets
for help on using tickets.