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... 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!
On Mar 23, 5:56 pm, James Bennett <ubernost...@gmail.com> wrote: > On Tue, Mar 23, 2010 at 3:57 PM, jrs <j...@framemedia.com> wrote: > > It is precisely due to this that I'm surprised the ORM has > > cascading deletes on by default. Seems to me that cascades should > > only happen when the app developer specifies, not the other way > > around... it's dangerous and I'm certain that many developers were bit > > by this. > > Then I guess you and all those other developers should start lobbying > database vendors to stop building referential integrity by default > into their products, since vendors like PostgreSQL have exposed far > more people to this "danger" than Django has... > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." -- 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.
