Re: OneToOneField unchangeable

2008-04-13 Thread Manuel Meyer
> On Sun, Apr 13, 2008 at 8:34 AM, Manuel Meyer > <[EMAIL PROTECTED]> wrote: > > > No, that's they way it is documented as working. The one-to-one > > field acts as the primary key for the model, and primary keys can't > > be edited. From http://www.djangoproject.com/documentation/model- > > a

Re: OneToOneField unchangeable

2008-04-13 Thread Karen Tracey
On Sun, Apr 13, 2008 at 8:34 AM, Manuel Meyer <[EMAIL PROTECTED]> wrote: > > > No, that's they way it is documented as working. The one-to-one > > field acts as the primary key for the model, and primary keys can't > > be edited. From http://www.djangoproject.com/documentation/model- > > api/#on

Re: OneToOneField unchangeable

2008-04-13 Thread Manuel Meyer
> No, that's they way it is documented as working. The one-to-one > field acts as the primary key for the model, and primary keys can't > be edited. From http://www.djangoproject.com/documentation/model- > api/#one-to-one-relationships: > > This OneToOneField will actually replace the prima

Re: OneToOneField unchangeable

2008-04-10 Thread Karen Tracey
On Thu, Apr 10, 2008 at 10:31 AM, Manuel Meyer <[EMAIL PROTECTED]> wrote: > > Hey, > > I have a type Article in which i hold a Type HeaderImage within an > OneToOneField-Relationship. > When adding an article via contrib.admin interface everything works > as expected. > But if I edit an existing a

OneToOneField unchangeable

2008-04-10 Thread Manuel Meyer
Hey, I have a type Article in which i hold a Type HeaderImage within an OneToOneField-Relationship. When adding an article via contrib.admin interface everything works as expected. But if I edit an existing article, the drop-down list doesn't appear anymore. class Article(models.Model):