So just to be clear, when using sqlite with foreign keys to a table with a
UUID primary key, x_id fk is a string with a UUID hex value (no dashes),
x.id is a type UUID value
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Djang
Refer to issue https://code.djangoproject.com/ticket/27595
This problem is broader than admin. It arises because if the scenario
described in the ticket is used (UUID foreign keys on Sqlite3), then what
is stored in myforeignkey_id is a string containing a uuid value without
any dashes, i.e. a
ppear that I am going to have to go from
1.8 to 1.9 hard without being able to have code pass tests in both at the
same time - unless I introspect the Django version. It would have been
better if this change had have gone through a deprecation cycle.
Cheers,
Wayne Merry
--
You received this me