id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
12587	Related fields when using multiple databases and different managers	aprilmay	nobody	"Let's take the case:

- 2 databases in settings.py (default and otherdb)

- 2 model managers, that will be used for managing models on different DBs:

{{{
class Manager1(models.Manager):
    def __init__(self):
        super(Manager1, self).__init__()
        self._db = 'default'

class Manager2(models.Manager):
    def __init__(self):
        super(Manager2, self).__init__()
        self._db = 'otherdb'
}}}
 
- 2 models using a manager each, and a relation between the 2:

{{{
class MyModel1(models.Model):
    objects = Manager1()

class MyModel2(models.Model):
    objects = Manager2()
    rel_to_model1 = models.OneToOneField(MyModel1)
}}}

In that case the relations fail:
{{{
a_model2 = MyModel2.objects.all()[0]
a_model1 = a_model2.rel_to_model1
}}}
The last line raises an error because it uses the manager for model2 for searching model1.

Also, 
{{{
a_model1 = MyModel1.objects.all()[0]
a_model2 = a_model1.mymodel2
}}}
The last line raises an error for the same reason than above.

These examples show (and the proposed patch is a fix for) the OneToOneField relation, but other relations might suffer from same kind of issue.

This is dummy code, hope it is good enough."		closed	Database layer (models, ORM)	dev		duplicate	multiple related		Unreviewed	1	0	0	0	0	0