It would be nice if both the trunk as well as multi db fully qualilfied all field names with db.table.field name.... I think that if this was done, the trunk could actually support multiple databases as long as the login credentials were the same for all databases and they were on the same server...although I could be wrong here.
This was one of the first things I had intended on investigating after the trunk was merged back in to this branch...as I'm having to do some nasty work arounds for this at the moment ( basically I do a query getting a list of all the id's that I need...then do a second query to retrieve those records from the other database.... the cross database query seems to only fail about 25% of the time ... and that is when i do this ). Ben... let me know when you have your repository public...and I'll give downloading it a shot as soon as our network guy fixes access to my server I was working with ... I can then co-ordinate with you about the rest of the merges... if you are comfortable doing them, since you've gotten quite far, that is fine, or I could give doing it a shot for some of the rest of them. Let me know. On Jun 8, 2:17 am, "Ben Ford" <[EMAIL PROTECTED]> wrote: > >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 -~----------~----~----~----~------~----~------~--~---
