You could just have a second database connection - to the same database but with a different prefix. Then in the models for the beta site application set the appropriate var $useDbConfig to point to the beta tables.
On Jun 20, 2:54 am, "Siebren Bakker" <[EMAIL PROTECTED]> wrote: > I have a website that I am building. It contains 2 cake applications, the > main website athttp://someiste.com, and a beta version of the website at > beta.somesite.com. > Each of these websites are currently accessing the same tables from the same > databse. I would like to split some of the tables to different ones, while > allowing some of them to be shared as well. > I.E. I would like my Users and Profiles to be shared across both > applications, but would like my Updates table to be separate for each site, > as the beta site will be updated whenever I add code/functionality, while > the main website will only be updated during a set period of time on a > daily/weekly basis. I would like to use the same database for each one > (would probably be easier then too), but for those tables that are specific > to the beta site, name the table say beta_updates, and the main one just > updates as it already is. > > Does anyone know who I could go about doing this, or could point me out to > any examples of anyone doing something similar to this. > > In the name of Life, Liberty, and the pursuit of my sanity. > Siebren Bakker(Aevum Decessus) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
