On 2/27/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > This sounds great to me. Go for it!
Ok - I've just committed these changes (r2409). As a result of this commit, there is one more unit test failing - in the many_to_one test, accessing new_article2.reporter.id seems to be getting a stale value from the cache when an article that is already a member of one reporters article set is added to a different reporter. If I change the test to check new_article2.reporter_id, the test passes, and if I look at what is in the database, it is correct - it's just the cache that is stale. Am I missing something obvious here, or is this a larger problem with the cache? I seem to recall a recent discussion about caching primary key lookups... 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 django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
