Re: When to create a new database

[Johan De Meersman]

- Original Message -
> From: "Ron Piggott" 
> Subject: Re: When to create a new database
>
> I would lean towards keeping it all together because of the speed
> decrease between connecting to different databases.

Heh, that consideration is a matter of semantics, and I'd guess you're used to 
Oracle? :-p

What OP (presumably) meant was "in different schemas". Terminology is 
important, y'all.


-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: When to create a new database

[Johan De Meersman]

- Original Message -
> From: "Reindl Harald" 
> Subject: Re: When to create a new database
> 
> it makes zero sense since you can use different users for the same
> database down to table and even column permissions

No, it does make some sense in the case where part of the dataset is going to 
be accessed by multiple independent applications, and I think the generic 
sports bits may actually fit that. It's cleaner from a design point of view, 
and it prevents accidentally deleting that data when the original application 
is taken out of production.

In my particular environment, we have quite a few of these generic databases; 
although from similar design ideology, they are also accessed only through 
their own REST interfaces, and not directly.

/Johan

-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql