|
@@ -283,21 +283,23 @@ number of SQL queries. For example::
|
|
|
Entry(headline="Python 3.1 Planned")
|
|
|
])
|
|
|
|
|
|
-Is preferable to::
|
|
|
+...is preferable to::
|
|
|
|
|
|
Entry.objects.create(headline="Python 3.0 Released")
|
|
|
Entry.objects.create(headline="Python 3.1 Planned")
|
|
|
|
|
|
Note that there are a number of :meth:`caveats to this method
|
|
|
-<django.db.models.query.QuerySet.bulk_create>`, make sure it is appropriate for
|
|
|
-your use case. This also applies to :class:`ManyToManyFields
|
|
|
-<django.db.models.ManyToManyField>`, doing::
|
|
|
+<django.db.models.query.QuerySet.bulk_create>`, so make sure it's appropriate
|
|
|
+for your use case.
|
|
|
+
|
|
|
+This also applies to :class:`ManyToManyFields
|
|
|
+<django.db.models.ManyToManyField>`, so doing::
|
|
|
|
|
|
my_band.members.add(me, my_friend)
|
|
|
|
|
|
-Is preferable to::
|
|
|
+...is preferable to::
|
|
|
|
|
|
my_band.members.add(me)
|
|
|
my_band.members.add(my_friend)
|
|
|
|
|
|
-Where ``Bands`` and ``Artists`` have a many-to-many relationship.
|
|
|
+...where ``Bands`` and ``Artists`` have a many-to-many relationship.
|