> Because I deleted that object. Delete method should be non-reversible > (except in transactions) like "del" statement in Python. Or anybody > knows any reason, why it should be reversible?
You didn't delete the object. That'd be spelled ``del instance``. You called a method called ``delete`` on an instance of a ``Model`` object. This is documented as deleting the row in the database that the object represents. You then called a method named ``save`` on a ``Model`` instance. This is documented as performing an insert if the row in question does not exist. If it doesn't behave the way you want it to, I'm sorry. But this is "correct" behavior: it matches the documentation, and both of them match the design. Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
