On Thursday, July 19, 2012 10:15:50 AM UTC-4, Gijs Molenaar wrote: > > hi Michael, > > Thanks for your response! One more question, see below. > But the test script has != hardcoded in it, is it the idea that you scan > every query for such character combination? Isn't this bad practice since > it will have a performance impact since it is performed on all queries?
Correct. You need to check and fix all queries. The overhead of a single, compiled regex replace per query should be negligible. The django-mssql backend does a lot more lifting than that for any query with aggregates or slicing. Regards, Michael Manfre -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/cKMiQzb3-04J. 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?hl=en.
