Russell Keith-Magee wrote:
> The serializer modeltests is probably your best bet if you are looking
> for examples. However, it's a pretty straightforward interface -
>
> for obj in serializers.deserialize("python", data):
> obj.save()
I'm just curious... when the multi-db branch comes in, is this something
where you could have 2 database settings and you could serialize with
data from DB1 and de-serialize to DB2?
I can't think of a reason why you'd want to do something like that in a
production environment but for what I'm after it would be kinda cool.
-Rob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
