On 03/23/2010 06:22 PM, jrs wrote:
Another great example... If PostgreSQL has referential integrity on by default, is django still hammering the db with unnecessary queries? I've already seen that it does when MySQL has referential integrity on... It seems people are confirming the django problem...
What Django problem? All I've read are assertions about how the default behaviour of enforcing referential integrity is bad without any proof that there is a problem. What you portray as a flaw, I view as a virtue.
I'm not trying to argue doing away with referential integrity, I'm arguing that django should not force the developer to accept it's unnecessary pummeling of the db when integrity is being maintained in some other way, such as postgreSQL built in functionality... I thank you guys for making my point more clearly than I've been able to!
What are these unnecessary queries you speak of? Can you show the SQL that is actually being sent to your back-end, which I'm guessing is MySQL?
-- Regards, Clifford Ilkay Dinamis 1419-3266 Yonge St. Toronto, ON Canada M4N 3P6 <http://dinamis.com> +1 416-410-3326 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
