On Tue, 2009-03-24 at 20:40 -0400, Karen Tracey wrote: [...] > > But the decision was made to not add this overhead to the start of > every connection. If you read the last paragraph you'll note it wasn't > an emphatic "no, never shall we do this" type of decision but I don't > know that anything has come to light to change the decision here, > other than a couple of people have noticed the oddness.
I think it's pretty emphatic these days. I wasn't rushing to judgement at the time, but nothing has happened in the interim to convince me that sort of change would be a good idea. We consistently reflect the database server's behaviour throughout Django. This is another case of that. If people choose MySQL, they get to experience all the consequences of that choice, both good and bad. I'd be strongly against changing it now. Adding extra overhead to every single connection to work around something that 99.9% of normal code won't do anyway and can easily be avoided would be irresponsible. If somebody wants to pass in pk=None and doesn't want the MySQL behaviour to occur they can use a server that doesn't do that or configure it off (and remember to do that every single time they use a different MySQL install). In practice, though, simply not sending through pk=None is the easy solution (that's how Django works internally for example). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
