I've run into a strange issue with using a UUID as primary key, and I'm
hoping we can either verify this is a bug, or figure out what I've done
I've got a core model object with a UUID for it's primary key. (Generated
external to this system, thus using that for when additional information
comes in.) And there are other model objects referencing it. Normally
everything runs fine. But after a while, web pages that have been running
fine start telling me that the UUID isn't valid (even though it is). (Sorry
I don't have a copy of the error at this moment, I'll post here when it
happens again.) I know it's not a simple coding error, because I can simply
restart Apache and everything is fine again. And these aren't POST
responses or anything complex like that. It occurs on a simple listing page.
When I dig into the exceptions, I see something that seems contradictory.
It looks like the UUID constructor has been called with an instance of a
UUID (it says type UUID doesn't have method 'replace'). But it doesn't seem
like that should be possible because the code that calls that constructor
first checks the type. (See django/db/models/fields/__init__.py -
So it's a double head scratcher. Once this problem crops up, I have to
restart the web server (but then it's okay for a while). And the errors it
gives me don't make much sense.
I don't know what kind of caching problem it could be - I haven't enabled
any of the available caching systems. Also doesn't seem to crop up (at
least not as often) in the built in dev test server.
Anyone seen this, or have any ideas?
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.