#25615 closed Bug (invalid)
multidb Relation fields do not support nested lookups — at Version 4
Reported by: | gerdkoetje | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.8 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
He all,
Does anyone know why i can't do any relation lookups on any database other then the default database in 1.8.5 this worked fine in 1.6.1
it keeps trowing me: Relation fields do not support nested lookups
for example on
adds = ProfielenFlirts.objects.filter(vooruserprofielenuserprofilefictief=True).filter(Q(antwoord=) | Q(antwoordisnull=True)).count()
ProfielenFlirts is a non default database, the relation lookup is in the same database do.
my router
class DatingRouter(object):
def db_for_read(self, model, hints):
if model._meta.app_label == 'datingmodels':
return 'dating'
return 'default'
def db_for_write(self, model, hints):
if model._meta.app_label == 'datingmodels':
return 'dating'
return 'default'
def allow_relation(self, obj1, obj2, hints):
if obj1._meta.app_label == 'datingmodels' and obj2._meta.app_label == 'datingmodels':
return True
elif 'datingmodels' not in [obj1._meta.app_label, obj2._meta.app_label]:
return True
return False
def allow_syncdb(self, db, model):
if db == 'dating' or model._meta.app_label == "datingmodels":
return False # we're not using syncdb on our legacy database
else: # but all other models/databases are fine
return True
any help would be appriciated
Change History (4)
comment:1 by , 9 years ago
Component: | Uncategorized → Database layer (models, ORM) |
---|---|
Type: | Uncategorized → Bug |
comment:2 by , 9 years ago
Summary: | multidm Relation fields do not support nested lookups → multidb Relation fields do not support nested lookups |
---|
comment:3 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | → needsinfo |
Status: | new → closed |
comment:4 by , 9 years ago
Description: | modified (diff) |
---|
test project proving this issue
https://github.com/gerdkoetje/dualdbtest
Please provide a minimal sample project that works on 1.6 and fails on 1.8. The simpler you can make the sample project, the easier it will be to determine if it's a bug in your application or in Django. Thanks!