blocks|key|627063|text|我做了类似的事情，不是用JSON，而是用xml，我的django是1.7，所以它可能不适合你。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627064|627065|您可以在引用序列化对象时使用natural+keys。如果索引已经被其他对象使用，这将防止混淆项目。|ordered-list-item|offset|length|627066|您可以使用dependencies来定义序列化的顺序(也就是deserialization).|627067|627068|也许像this+one这样的类似帖子也是有帮助的。|627069|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/dev/topics/serialization/#natural-keys|1|https://docs.djangoproject.com/en/dev/topics/serialization/#dependencies-during-serialization|2|https://stackoverflow.com/questions/6164604/serialize-django-models-with-reverse-one-to-one-fields-to-json^0|0|0|E|C|0|0|5|C|1|0|0|3|8|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@$F|15|G|16|1|17]]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|19|8|@]|9|@$F|1A|G|1B|1|1C]]|A|$]]|$1|M|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

I did something similar, notwith JSON but with xml, and my django is 1.7, so maybe it does not work for you.

<ol>
<li>You can use <a href="https://docs.djangoproject.com/en/dev/topics/serialization/#natural-keys" rel="nofollow noreferrer">natural keys</a> when you are referencing serialized objects. This will prevent mixing up items if the index is already used by an other objject. </li>
<li>You can use <a href="https://docs.djangoproject.com/en/dev/topics/serialization/#dependencies-during-serialization" rel="nofollow noreferrer">dependencies</a> to define the order of serialization (and therefore deserialization).</li>
</ol>

Maybe similar posts like <a href="https://stackoverflow.com/questions/6164604/serialize-django-models-with-reverse-one-to-one-fields-to-json">this one</a> are helpful as well.

blocks|key|2942610|text|在转储数据fixture时，请确保使用--natural参数：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2942611|python+manage.py+dumpdata+myapp+--indent=4+--natural|code-block|syntax|javascript|2942612|https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-option---natural|offset|length|2942613|它看起来在1.7中被弃用了--自然的--外来的|2942614|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|2D|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@]|9|@$I|W|J|X|1|Y]]|A|$]]|$1|K|3|L|5|6|7|Z|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|H]]]]

When you dump your data fixtures, make sure you use the --natural argument:

<pre><code>python manage.py dumpdata myapp --indent=4 --natural
</code></pre>

<a href="https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-option---natural" rel="nofollow">https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-option---natural</a>

It looks its being deprecated in 1.7 for --natural-foreign

blocks|key|627040|text|您可能最终会使用South，这使得数据迁移既简单又强大：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|627041|http://south.readthedocs.org/en/latest/about.html|offset|length|627042|随着Django1.6的到来，新的migrations+module将取代旧的数据库命令，并使South过时。|627043|entityMap|0|LINK|mutability|MUTABLE|url|1|https://docs.djangoproject.com/en/dev/topics/migrations/^0|0|0|1D|0|0|H|H|1|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]|O|$5|K|L|M|A|$N|P]]]]

You may end up using South, which makes data migrations both easy and powerful:

<a href="http://south.readthedocs.org/en/latest/about.html" rel="nofollow">http://south.readthedocs.org/en/latest/about.html</a>

Coming with Django 1.6, a new <a href="https://docs.djangoproject.com/en/dev/topics/migrations/" rel="nofollow">migrations module</a> will replace the old database commands and make South obsolete.

blocks|key|627112|text|实际上，如果您想要使用dumpdata和loaddata等命令来备份和恢复数据库中的选定对象，那么O2O关系可能会变得很棘手。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|627113|我们的软件也有类似的问题，我发现一个可行的解决方案是覆盖django.core.serializers.base.DeserializedObject上的save()方法，以便在保存"double“对象之前获得一个句柄。此时，您可能决定丢弃由Django创建的默认O2O关系，并让框架保存新关系或使用存储在您的XML或JSON文件中的值更新它。|627114|但是，在执行loaddata命令之前，您必须将被覆盖的方法放在Django拾取的某个位置。一种可能是创建您自己的命令，该命令依次调用loaddata。在命令模块中，您可以安装覆盖。此解决方案包含以下详细信息：|627115|使用Django+1.8.x测试的|627116|unordered-list-item|627117|我们的O2O字段被附加到Django+User模型|627118|为简单起见，在本例中，我将附加的O2O字段称为Attached.|627119|627120|627121|#+Overrides+deserialization+to+affect+OneToOneFields+for+Users+correctly
import+django.core.serializers.base
from+django.contrib.auth.models+import+User
from+your.attached.models+import+Attached+#model+with+O2O+field+to+User

_original_save+=+django.core.serializers.base.DeserializedObject.save

def+save(self,+*args,+**kwargs):

++++if+isinstance(self.object,+Attached):
++++#+if+the+user+in+question+has+an+attached+object,+delete+it
++++user+=+User.objects.get(pk=self.object.user_id)
++++if+hasattr(user,+'attached'):+user.attached.delete()

++++#+use+the+built-in+function+for+all+other+cases
++++_original_save(self,+*args,+**kwargs)

django.core.serializers.base.DeserializedObject.save+=+save|code-block|syntax|javascript|627122|如果您在if+hasattr(...)子句中避免了删除，使用来自序列化对象的值更新现有对象并跳过对_original_save()的调用，则可以修改上面的代码，而不是删除现有对象，而是更新它。这将使代码与模型更紧密地联系在一起，因为您可能必须定义要在现有对象上更新哪些字段。上面显示的解决方案没有对模型的内容进行任何假设。|627123|entityMap^0|B|8|K|8|0|S|1B|25|6|0|6|8|1U|8|0|0|0|J|4|0|N|8|0|0|0|0|4|F|1D|G|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1H|8|@]|D|@]|E|$]]|$1|L|3|-4|5|M|7|1I|8|@]|D|@]|E|$]]|$1|N|3|O|5|M|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|M|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|T|3|U|5|V|7|1R|8|@]|D|@]|E|$W|X]]|$1|Y|3|Z|5|6|7|1S|8|@$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1X|8|@]|D|@]|E|$]]]|11|$]]

Indeed, O2O relationships can get tricky if you want to use commands such as <code>dumpdata</code> and <code>loaddata</code>, for example, to backup and restore select objects in your database.

We have a similar issue with our software and I found that a possible working solution would be to override the <code>save()</code> method on <code>django.core.serializers.base.DeserializedObject</code> to actually get a handle into the moment just before the "double" object is saved. At this point, you may decide to throw away the default O2O relation created by Django and let the framework save the new one or update it with the stored values on your XML or JSON file.

You'd have to put the overwritten method somewhere Django picks up before the <code>loaddata</code> command is executed though. One possibility is to create your own command that in turn calls <code>loaddata</code>. In the command module, you install the override. The following details on this solution are implied:

<ul>
<li>Tested with Django 1.8.x</li>
<li>Our O2O field is attached to the Django <code>User</code> model</li>
<li>For the sake of simplicity in this example, I'll call the attached O2O field <code>Attached</code>.</li>
</ul>

<hr>

<pre><code># Overrides deserialization to affect OneToOneFields for Users correctly
import django.core.serializers.base
from django.contrib.auth.models import User
from your.attached.models import Attached #model with O2O field to User

_original_save = django.core.serializers.base.DeserializedObject.save

def save(self, *args, **kwargs):

 if isinstance(self.object, Attached):
 # if the user in question has an attached object, delete it
 user = User.objects.get(pk=self.object.user_id)
 if hasattr(user, 'attached'): user.attached.delete()

 # use the built-in function for all other cases
 _original_save(self, *args, **kwargs)

django.core.serializers.base.DeserializedObject.save = save
</code></pre>

You may modify the code above for, instead of deleting the existing object, updating it if you, at the <code>if hasattr(...)</code> clause, avoid the deletion, update the existing object with the values coming from your serialized object and skip the call to <code>_original_save()</code>. It will make the code a bit more tied to model though, as you may have to define which fields to update on the existing object. The solution shown above makes no assumption on the contents of the model.

As stated <a href="https://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance">here</a> objects are created automatically for models with OneToOne relationship to other models. So if I have Model1 with O2O to Model2, and will create object of Model2 with pk=1, then object of Model1 with model2_id=1 will be created autmatically. Then, if Ill dump data from DB to json, I will have two records for these objects. And if I will try to load this data to DB with <code>loaddata</code> - it will fail, because object for Model2 will be created twice and it will cause unique index violation and <code>IntegrityError</code>. 
Does anybody found sane solution for this?

p.s. 
I use Django 1.3.7

Django fixtures and OneToOneField

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如上所述，对于与其他模型具有OneToOne关系的模型，对象是自动创建的。因此，如果我将Model1与O2O连接到Model2，并将使用pk=1创建Model2的对象，那么将自动创建Model1与model2_id=1的对象。然后，如果我将数据从DB转储到json，我将拥有这些对象的两条记录。如果我试图用loaddata将这些数据加载到数据库中-它将失败，因为Model2的对象将被创建两次，这将导

问Django fixtures和OneToOneField
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django fixtures和OneToOneFieldEN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django fixtures和OneToOneField
EN