Changes between Version 4 and Version 5 of Ticket #24012, comment 4
- Timestamp:
- Dec 18, 2014, 7:07:39 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #24012, comment 4
v4 v5 1 If you look here: [https://github.com/django/django/blob/108b8bf852c76855ed98f5abe55db1da845598e7/django/db/models/fields/__init__.py#L2261 here] you see that `models.UUIDfield` forces data to fit into uuid.UUID even when the DB allows other formats also. This check, and the requirement to store the content of the UUIDfield in a uuid.UUID object is the main issue.1 If you look here: [https://github.com/django/django/blob/108b8bf852c76855ed98f5abe55db1da845598e7/django/db/models/fields/__init__.py#L2261 here] you see that `models.UUIDfield` forces data to fit into uuid.UUID even when the DB allows other formats also. In my naive view, this check, and the requirement to store the content of the UUIDfield in a uuid.UUID object is the main issue. 2 2 3 3 the `field` DDL is a RAW(16) or RAW(32). However the data is generated by Oracle SYS_GUID(), which generates a raw(16) which in turn translates into a 32-character hex string. I cannot print it directly (thats the whole point of this ticket). The hex representation is: 0a6ce74693a906b6e0535799030a228e .