#2331: Related Field has invalid lookup: icontains
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by mtredinnick):
OK, ignore my last comment, it was lazy. I looked at the code. Suspicion
falls on [3246], but it looks like Russell was not expecting non-standard
primary keys in there (maybe?). Are you seeing this on a model that has a
custom primary key? If not, why on earth are we in that method?
I'm reluctant to go diving in here trying to fix edge cases whilst Adrian
is doing his refactoring. The odds of a patch surviving are small. The
whole query dissecting and processing phase is possibly open on his lab
table with entrails all over the place.
--
Ticket URL: <http://code.djangoproject.com/ticket/2331>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
