Anyone who mixes the ORM with raw data-modifying SQL concurrently may well be in for a surprise.
Scenario. Load your model; run your data-modifying SQL; then explicitly try to reload your model to refresh it's data. Gotcha. The inbuilt queryset cache will cleverly skip straight over your attempt to reload. Only way around this I propose is some kind of .reload() method. We can't openly endorse using raw SQL alongside the caching ORM and not have one. See ticket for background, and a possible patch -- http://code.djangoproject.com/ticket/901 --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
