Re: Seems like a geodjango bug with multiple databases

Hi, sorry for my late response. Thanks for replying. I'm using django 1.7.4. Going with this Room.objects.using('another').select_related('hotel').get(pk=10) is fine, I can then get room.hotel without any problem. I also followed Jani's advice and changed default manager of Room to GeoManage

Seems like a geodjango bug with multiple databases

I'm using geodjango and multiple databases, and experiencing a quite weird situation, I guess it's a kind of bug but not absolutely sure since I'm pretty new to Django. Here is how to reproduce the problem: - Set up another database besides default: DATABASES = { 'default': { 'ENGINE' : 'django.