Ramsey is right. There are lots of pitfalls.
Losing FK constraints is a pain and I miss it, but it's something I can deal
with … not ideal, but not a killer.
Reassigning IDs and merging data is the biggest problem and we are helped by
the fact that most of our data comes to us and is loaded from
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
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 databa
Thanks Pascal.
I downloaded the application, I am trying to understand how it works but it is
not clear to me.
I will study it.
Thanks for the hint.
Miguel Torres.
On 20/12/2012, at 17:56, Pascal Robert wrote:
> Use this:
>
> https://github.com/hprange/multi-tenant-prototype
>
>> Hi list,
Hi Micheal,
Do you have any code to share that shows how to change the data base connection
information of the model on the fly?
On 20/12/2012, at 18:01, 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
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 D
Use this:
https://github.com/hprange/multi-tenant-prototype
> 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
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 informa
