On 9/15/06, Vizcayno <[EMAIL PROTECTED]> wrote: > > Russell: > The error happens using the Admin view. > I need to rectify one thing pleaaaaase, I beg your pardon, instead of > modifying Fredo to Frido please, modify for example Maria to Mario, > i.e. when I modify the data that has DATA3 as X and this data is > related to other record in the same table, the relation dissapears. > I send you all the files I used:
It looks to me like the admin view is doing exactly what you asked it to. Your model has a m2m relation on self, that says that only instances with data3=True can be selected. - You add Pepe, Sue, and Fredo. The data4 list will only show instances with data3=True, so the list options are Maria, Jose and David. You select Maria. - You then edit Maria. Again, the data4 list will only show instances with data3 = True, so the list options are... Maria, Jose and David. Pepe, Sue and Fredo all have data3=False, so they cannot appear in this list. The relation is symmetric, so when you save to change Maria to Mario, the list is cleared of all non-data3=true members. - You go back to Pepe. Pepe no longer has Maria (or mario) set. When you saved Mario, you specified that Mario had no related objects, so Pepe cannot have Mario as a related object. If you were to make the relation non-symmetric, this problem would go away, but you would end up with a different set of problems where Pepe could be related to Mario, but Mario was not related to Pepe. The problem here is caused by your filter, which cannot be applied symmetrically. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
