mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 10:34:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #10647: intermediary tables between two umanaged models are no longer created.

Browse source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10455 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jacob Kaplan-Moss 2009-04-09 15:03:31 +00:00
parent f55f2b9d74
commit c0ad626dca
4 changed files with 55 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/ref/models/options.txt
View file

@ -98,11 +98,16 @@ model handling are exactly the same as normal. This includes
specify all the columns from the database table you are modeling when
using unmanaged models.
2. If a model contains a :class:`~django.db.models.ManyToManyField` and
has ``managed=False``, the intermediate table for the many-to-many join
will also not be created. Should you require the intermediate table to
be created, set it up as an explicit model and use the
:attr:`ManyToManyField.through` attribute.
2. If a model with ``managed=False`` contains a
:class:`~django.db.models.ManyToManyField` that points to another
unmanaged model, then the intermediate table for the many-to-many join
will also not be created. However, a the intermediary table between one
managed and one unmanaged model *will* be created.
If you need to change this default behavior, create the intermediary
table as an explicit model (with ``managed`` set as needed) and use the
:attr:`ManyToManyField.through` attribute to make the relation use your
custom model.
For tests involving models with ``managed=False``, it's up to you to ensure
the correct tables are created as part of the test setup.