Re: solving fixture data conflicts

2008-03-04 Thread Russell Keith-Magee
On Wed, Mar 5, 2008 at 1:34 PM, Evan H. Carmi <[EMAIL PROTECTED]> wrote: > > Russell Keith-Magee wrote: > > The only real solution at present is to avoid serializing content > > types whenever possible (i.e., by not dumping the contenttypes > > application). If your fixture already has content

Re: solving fixture data conflicts

2008-03-04 Thread Evan H. Carmi
Russell Keith-Magee wrote: > The only real solution at present is to avoid serializing content > types whenever possible (i.e., by not dumping the contenttypes > application). If your fixture already has content types, manually > delete them from the fixture before loading. How can I go about man

Re: solving fixture data conflicts

2008-03-04 Thread Russell Keith-Magee
On Tue, Mar 4, 2008 at 3:59 PM, Evan H. Carmi <[EMAIL PROTECTED]> wrote: > > Hi, > > I am trying to loaddata from a file, bmdata.xml and getting an error: > Problem installing fixture 'bmdata.xml': duplicate key violates unique > constraint "django_content_type_app_label_key" > > I understand

solving fixture data conflicts

2008-03-03 Thread Evan H. Carmi
Hi, I am trying to loaddata from a file, bmdata.xml and getting an error: Problem installing fixture 'bmdata.xml': duplicate key violates unique constraint "django_content_type_app_label_key" I understand that there is a conflict in the fixture data. However, I don't know how to solve it. I only