On 6/27/06, Mikko Nylén <[EMAIL PROTECTED]> wrote: > > As said in the ticket, the current behavior would probably be quite trivial > to change and would result in more natural way to filter/get objects -- not > to mention, it would allow the get_or_create() to work properly.
I've had a look at this - you are correct; the fix is relatively simple (just need a get_db_prep_lookup method on ForeignKey, etc). However, building up some unit tests to validate the change has revealed some other problems with lookups (especially reverse lookups). I'm working on fixing these at the moment. Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
