I noticed that Django handles all the referential integrity issues for delete statements at the Python/ORM level. - Is this documented anywhere?
Furthermore I can't seem to find a switch to turn the whole ORM/python level referential stuff off. Is there a setting for this somewhere? (I prefer the database to handle it) Also, there is no support for different actions upon a delete. Basically like this ticket sais: http://code.djangoproject.com/ticket/2288 I have a logging table with relations to my production tables. They are relations but no action would be more appropriate. The only way to do this seems to be a IntegerField, instead of a ForeignKey. Is there any alternative. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
