>The Model should probably be keeping track of the database it is on,
>rather than the field. The model base already tracks column names and
>the like; adding a database name wouldn't be out of place. Then, if a
>field references a model, you can compare the remote model's database
>name with the local model.
Essentially, that's what this bit is doing:
rel.to._default_manager.connection
In muti-db the model's default manager keeps a reference to the db.
I'll see if i can have a play with the tests and nail it down a bit
better!
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
