Some answers... In my particular case, I may not even need to worry about the has_many relationship from A to B. If all I need to take advantage of is the fact that B belongs_to A, _and_ I'm sure that my keys are all consistent, then simply doing
belongs_to :a, :foreign_key => 'appropriate_foreign_key' will be fine since "belongs_to" only generates a query on the parent table and isn't trying to talk to both model tables at once. And even if I do need the has_many relationship, it is easiest to simply define the appropriate "bs" (that's as in the plural of "b") method on A which can just go directly to the B table and filter it based on the foreign key. None of this cross-DB stuff is really necessary. Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
