[eluser]jleequeen[/eluser]
[quote author="jleequeen" date="1223503030"]@xwero
I suppose that could work, but seems a little more complex a solution than I am looking for. Maybe a simple example would explain what one of my issues is. I currently have app1 that uses db1 and app2 that uses db2. I suppose you could almost say that app2/db2 is a sub application to app1/db1 in that, users are created in and stored in db1, and db2 has tables that reference the users in db1. What I want to keep is continuity between the two databases. So if a user gets deleted in db1...db2 is updated as well. I use MySQL by the way. In my app1 model I have a function that goes into each table where said user exists and deletes it, but I don't have that model doing anything in db2. I've had apprehension about letting a model in one app make changes in another database. It just seems that applications could become very interdepent if I started doing that. But maybe that is ok. Just never worked with multiple apps that had multiple databases all living as one big happy family.
Do you think that it is good or bad to manipulate multiple databases from within one apps model?[/quote]
Did anyone have a chance to ponder my question above?