Re: Reverse relation lookups with multidb

2015-10-27 Thread probleem support
Thanks a lot tim, this has resolved the issue. Lesson learned to jump from 1.6 to 1.8 go release by release. then i would probably seen it. Appreciated ur help do! -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group a

Re: Reverse relation lookups with multidb

2015-10-27 Thread Tim Graham
In order to use models and their relations you have to include them in INSTALLED_APPS regardless of which database they are stored in. This is noted in the 1.7 release notes: https://docs.djangoproject.com/en/1.8/releases/1.7/#app-registry-consistency Maybe you don't want your local project to

Re: Reverse relation lookups with multidb

2015-10-27 Thread probleem support
Tim in my real project that database is a remote database, that shouldn't be in installed apps shouldn't it. but to prove my point it did it with 2 local databases in the test project. in my real project i can't do reverse lookups on the remote database models. -- You received this message beca

Re: Reverse relation lookups with multidb

2015-10-27 Thread Tim Graham
As noted on the ticket, it looks like you're missing an app in INSTALLED_APPS. On Tuesday, October 27, 2015 at 10:55:51 AM UTC-4, probleem support wrote: > > test project proving my point > https://github.com/gerdkoetje/dualdbtest > -- You received this message because you are subscribed to the

Re: Reverse relation lookups with multidb

2015-10-27 Thread probleem support
test project proving my point https://github.com/gerdkoetje/dualdbtest -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com.

Re: Reverse relation lookups with multidb

2015-10-24 Thread probleem support
working on that -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@goog

Re: Reverse relation lookups with multidb

2015-10-24 Thread Tim Graham
It would be helpful if you could create a minimal example project (without unnecessary fields and methods) with a test that passes on Django 1.6 but fails on Django 1.8. On Saturday, October 24, 2015 at 9:13:42 AM UTC-4, probleem support wrote: > > this worked fine in django 1.6.1 but fails in

Re: Reverse relation lookups with multidb

2015-10-24 Thread probleem support
this worked fine in django 1.6.1 but fails in 1.8.5 -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this g

Re: Reverse relation lookups with multidb

2015-10-24 Thread probleem support
same for nieuweklanten = ProfielenUserprofile.objects.values('user__profielenprofielen__profielnaam')[:1] for nieuwe in nieuweklanten: print(nieuwe['user__profielenprofielen__profielnaam']) -- You received this message because you are subscribed to the Google Groups "Django users" group

Re: Reverse relation lookups with multidb

2015-10-24 Thread probleem support
> > nieuweklanten = ProfielenUserprofile.objects.all()[:1] >> for nieuwe in nieuweklanten: >> print(nieuwe.user.profielenprofielen.profielnaam) >> >> >> this for example works fine >> > but doing the same thing but then like this with works fine on i do a similar test on the default db but i

Re: Reverse relation lookups with multidb

2015-10-24 Thread Tim Graham
I don't think this has anything to do with multi-db. I'm not sure what that query is trying to accomplish. Can you simply use: ProfielenUserprofile.objects.values('profielnaam') You can't use values() across a reverse ForeignKey ("foo_set") as this might return multiple values. On Saturday,

Re: Reverse relation lookups with multidb

2015-10-24 Thread probleem support
we also tried without _set etc. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to d