Hello.
I've been developing on the multdb branch for awhile now (most recent
version just before the dropping of the 'using' meta attribute), and
everything has been going well. Recently though, with multidb landing
in the trunk, I wanted to switch over to the trunk.
I have a 'partitioning' scheme somewhat like this:
----db_extra
class Building(models.Model):
area = models.ForeignKey('area')
...etc
----default
class Area(models.Model):
...etc
And in db_extra, i've defined a custom manager that overrides
get_query_set(), returning .using('db_extra') as per the svn docs.
Now, my admin changelist includes the 'area' foreign key field on
Building. In the multidb branch, all was fine - the admin 'correctly'
retrived the foreign key id number from the db_extra db, and looked it
up locally in default. In the trunk now, I get a TemplateSyntaxError
indicating that the specified Area does not exist.
Clearly, it is now looking to the db_extra db for the related area
instead of looking to default.
Am I doing this correctly? How can I inform django to lookup the
foreign key in this db?
Thanks for any help.
-CB
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
