I found it! Karen you are right. I had already a field called "friends", with a different information. When I was using Attributes as an OneToOne relationship it was all ok, but when using it in inheritance, it fails, of course!
Thanks for your help On 2 mayo, 01:42, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Thu, May 1, 2008 at 5:13 PM, bcurtu <[EMAIL PROTECTED]> wrote: > > > Thanks, > > > Attributes is just a simple abstract class with some fields. Nothing > > special. > > See, though, I could not recreate any error with a nothing-special abstract > base class named Attributes that I made up myself. Guessing what might be > causing the error, I added a field named friends to the Attributes class, > and that does trigger the error you report. (I do not know why the message > says field of similar name instead of field with the exact same name.) Per > the docs > (http://www.djangoproject.com/documentation/model-api/#model-inheritan... > > "It is an error to have fields in the abstract base class with the same name > as those in the child (and Django will raise an exception)." > > If this is not the cause of your error, please post the details of the > Attributes definition and perhaps someone can spot what is causing the > problem. > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
