AFAIK, 'dashes' in a character based persisted UUID is divergent behavior.
UUID are 128 bits wide, apportioned by nibble into a character field, 32 at
most. So... The migration is yours to correct. Good luck, good hunting, HTH.
On Wednesday, May 4, 2022 at 11:14:02 AM UTC-4 bmila...@gmail.com wr
and curious why the change in this behavior vs using the db's native uuid
type directly
On Thursday, May 5, 2022 at 7:27:02 AM UTC-4 Jason wrote:
> when you print the query executed, what is the difference between a
> working query and the current one?
>
> On Wednesday, May 4, 2022 at 11:14:02
when you print the query executed, what is the difference between a working
query and the current one?
On Wednesday, May 4, 2022 at 11:14:02 AM UTC-4 bmila...@gmail.com wrote:
> Hello Django users,
>
> I've recently upgraded the Django version from 2.2 to 3.2 in a project at
> work. In this pro
Hello Django users,
I've recently upgraded the Django version from 2.2 to 3.2 in a project at
work. In this project, we've been using a custom version of UUIDField since
version 1.x without issues. The purpose of this field is to persist the
full UUIDs with dashes into the database (MySQL char(36)
4 matches
Mail list logo
