-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix prefetch related with UUID fields #35
base: master
Are you sure you want to change the base?
Conversation
Because the foreign key is stored as a string (char field) and the uuid field is returned as a UUID (StringUUID) object, prefetch related does not work. This patch makes StringUUID dict keys equivelent to string dict keys.
This fixes the prefetch related issue and does not break existing code since the .hex method can still be called on the StringUUID object. |
Looks good to me. Any concerns, @dcramer? |
The fix is not working when you are using |
def __hash__(self): | ||
return self.__unicode__().__hash__() | ||
|
||
def __eq__(self, other): | ||
return self.__unicode__().__eq__(unicode(other).replace('-', '')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
def __hash__(self): | |
return self.__unicode__().__hash__() | |
def __eq__(self, other): | |
return self.__unicode__().__eq__(unicode(other).replace('-', '')) | |
def __hash__(self): | |
return self.__unicode__().replace('-', '').__hash__() | |
def __eq__(self, other): | |
return self.__unicode__().replace('-', '').__eq__(unicode(other).replace('-', '')) |
Because the foreign key is stored as a string (char field) and
the uuid field is returned as a UUID (StringUUID) object, prefetch
related does not work.
This patch makes StringUUID dict keys equivelent to string dict
keys.