On Tue, Mar 16, 2010 at 5:25 PM, Justin Graf wrote:
>> Do not mix data from multiple applications in one database. Use
>> multiple databases to isolate them entirely.
>>
>>
> That's not always a practical solution to the problem,
>
> the Apps may need to share numerous tables, duplicating the data
On Tue, 2010-03-16 at 16:35 -0400, Vick Khera wrote:
> On Tue, Mar 16, 2010 at 3:03 PM, Jamie Kahgee wrote:
> > I'm curious what people consider best practice (or how do you do it) to
> > help ensure these name collisions don't happen.
>
> Do not mix data from multiple applications in one databa
On 3/16/2010 3:35 PM, Vick Khera wrote:
> On Tue, Mar 16, 2010 at 3:03 PM, Jamie Kahgee wrote:
>
>> I'm curious what people consider best practice (or how do you do it) to
>> help ensure these name collisions don't happen.
>>
> Do not mix data from multiple applications in one database.
On Tue, Mar 16, 2010 at 3:03 PM, Jamie Kahgee wrote:
> I'm curious what people consider best practice (or how do you do it) to
> help ensure these name collisions don't happen.
Do not mix data from multiple applications in one database. Use
multiple databases to isolate them entirely.
--
Sent
On Tue, Mar 16, 2010 at 1:03 PM, Jamie Kahgee wrote:
> My company has a handful of apps that we deploy in the websites we build.
> Recently a very old app needed to be included along side a newer app and
> there was a conflict w/ a duplicate table name needed to be used by both
> apps.
> We are n
My company has a handful of apps that we deploy in the websites we build.
Recently a very old app needed to be included along side a newer app and
there was a conflict w/ a duplicate table name needed to be used by both
apps.
We are now in the process of updating an old app and there will be some
