I ended up actually using a view in the second database which pulls from the repository database, then I defined a model on top of that view. I did this because the data that single model would be referring to was actually spread over many tables for the purposes of another (primary) commercial application. Send me a red flag if this sounds like a bad idea. :)
On Apr 9, 11:54 am, "nate" <[EMAIL PROTECTED]> wrote: > Yes. Just set up each database config in database.php, and choose > which one each model will use by setting var $useDbConfig = "x"; Then > associate your models as normal. Keep in mind, however, that cross- > database associations tend to generate more queries, since you don't > have the benefit of being able to do left joins and whatnot. > > On Apr 9, 9:31 am, "Joshua Benner" <[EMAIL PROTECTED]> wrote: > > > I'm preparing to dive into a Cake project. In this application, there > > will be basically just 3 tables which augment, describe, or link data > > that is found in several tables in a different data source (our > > primary data repository). Is it possible to associate models from > > different data sources? (technically, they're on the same SQL server, > > but in different databases) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
