On 6 juin 2014, at 09:42, Thomas Güttler <h...@tbz-pariv.de> wrote: > I think it is a "not invented here" syndrome: Ruby on Rails did it before. > That's > a reason to do it different.
The reason is more simple. Rails was designed around MySQL, a database with a rather casual relationship to data integrity. It will happily truncate data or save invalid values in the name of performance. In the same spirit STI trades data integrity for speed. It avoids joins, which can be very slow on MySQL, but also prevents the database from enforcing constraints. Django was designed around PostgreSQL, a database that cares about its data. That explains many differences in the design of the Rails and Django ORMs. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/E238DFA5-8938-4DBD-8E78-0D0B477ACA88%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
