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
On Wed, 18 Feb 2015 06:45:15 -0800 (PST)
Luan Nguyen wrote:
> 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 anothe
I'm using with success two postgis enabled databases on a single
application, without quirks.
I have a read-only database, and a read/write database. No problems, so far.
On Thu, Feb 19, 2015 at 5:11 PM, Collin Anderson
wrote:
> Hi,
>
> Interesting. What version of django is this?
>
> Here's so
Hi,
Interesting. What version of django is this?
Here's something to try:
Room.objects.using('another').select_related('hotel').get(pk=10)
It could very well be an issue with GeoManager / GeoQuerySet.
You also could ask on the geodjango list to see if anyone else has run into
that.
http://gro
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.
5 matches
Mail list logo
