I think you are right Ramsey, I already have the two databases and the project works well, but now I want to implement the solution for more that one enterprise and I am facing some troubles.
Maybe I should evaluate to migrate all to one database. Thanks. Miguel Torres On 20/12/2012, at 18:40, Ramsey Gurley <rgur...@smarthealth.com> wrote: > You lose FK constraints that way too. I would not break up the database if > you need relationships between the models. That includes in the future. > > Even if you don't have relationships, think about what happens when a client > with more than one enterprise wants to move data between the two databases or > possibly merge them? PK collisions, fk collisions. Nightmare code trying to > follow relationships and reassign IDs. > > Worst of all, I can imagine a day when the client will dream up some reason > why they need to relate data between DB1 and DB2. Then you are truly pooched. > No siree, I'd simply add a column to the model indicating which enterprise > the data belongs to and put everything in one database. Otherwise, I think > you're setting yourself up for a world of hurt. > > Ramsey > > On Dec 20, 2012, at 5:01 PM, Michael Gargano wrote: > >> yes, I'm doing that now. just be aware that cross db joins are a b*tch. >> if there are to many relations to join across you will quickly hit >> limitations with IN clauses (which will be your best friend). unless >> someone else has come up with something more clever than what I'm doing >> >> -Mike >> >> On Dec 20, 2012, at 6:45 PM, Miguel Torres <w...@toracom.net> wrote: >> >>> Hi list, >>> >>> We are developing an ERP application. >>> We want to use the following approach: >>> >>> One database to storage users, access control rules, application >>> configuration and an enterprises catalog. >>> >>> For each enterprise we want to set up a different database. >>> >>> For example: One ERP controlling information of two enterprises would need >>> three databases: >>> ApplicationDatabase >>> EnterpriseOneDatabase >>> EnterpriseTwoDatabase >>> >>> We are doing this because we believe this is more efficient in the long >>> term with clients that have more than one enterprise. >>> >>> We have two Data base Models in the application >>> >>> ErpApplicatioEOModel >>> ErpEnterpriseEOModel >>> >>> The main page is a Login form where the user selects the Enterprise she >>> wants to work with. After the user logins successfully we want to set the >>> database connection information in the ErpEnterpriseEOModel. >>> >>> Is that possible? >>> >>> >>> Thanks in advanced. >>> >>> Saludos, Miguel Torres. >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/mgargano%40me.com >>> >>> This email sent to mgarg...@me.com >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >> >> This email sent to rgur...@smarthealth.com >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
