Hi all, I'm trying to work out if Ticket #5030 is good to go or not. Basically, when save() is called on a model, django does a SELECT COUNT(*)... query to check that the primary key is good.
However, SELECT 1... is apparently quite a bit faster in many circumstances, and we should use it if we can. It looks like postgres, mysql, and sqlite all handle this nicely, but we're not sure about SQL Server and Oracle. If anyone knows, or can apply the patch and check, please let me know. Thanks, Simon #5030 - http://code.djangoproject.com/ticket/5030 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
