On Wednesday 13 September 2006 14:41, James Bennett wrote: > I've written about that in a "quick summary" sort of way; you might > want to read it: > http://www.b-list.org/weblog/2006/06/04/lets-talk-about-frameworks-dba-edit >ion
Thanks James, a nice "generic" summary. For my part I would summarise as follows: I have no objection whatsoever for a higher layer ORM to "fill in the gaps" and provide functionality where it is missing at the database level. To completely override the data integrity rules of a database entirely capable of looking after itself is utterly unforgivable. As for Django, I think some small parts of the ORM need to be re-examined to leave some of the data integrity and modification to the database engine itself if it is deemed capable. Oh, and put a warning in the docs about these multi table/multi row operations not being wrapped in a transaction unless you enable transactions yourself. Regards, Gary. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
