On Tue, 2008-03-25 at 05:51 -0700, sector119 wrote:
[...]
> I try to write my own comand to manage.py which imports data in some
> format to the db.
> I write my own serializer which yields
> base.DeserializedObject(self.model(**data), m2m_data).
>
> When I run deserlialized object save method I got IntegrityError -
> because I use unique_together = ('location', 'pid') and model's data
> violate unique constraint "people_person_location_id_key".
> But I think that does Django have to run UPDATE not INSERT here?
Firstly, Django only does an update if your model has an existing pk
value *and* that primary key value exists in the database. On the model
you've provided, neither pid, nor location are the primary key of the
model.
Secondly, you've added an constraint that says "amongst all the rows in
these tables, these two values must be unique as a pair". It doesn't say
"and update the corresponding row if they already exist", which is what
you're hoping would happen. That's because it is *not* the same row
(different primary key values mean different rows).
I think the solution here is that you need to fix the data you're
submitting to not include constraint-busting data, or else subclass the
deserializer and override the saving code to catch the error, delete the
existing element and resave.
Regards,
Malcolm
--
A clear conscience is usually the sign of a bad memory.
http://www.pointy-stick.com/blog/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
