- Original Message -
> From: "Ron Piggott" <ron.pigg...@actsministries.org>
> 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,
- Original Message -
> From: "Reindl Harald" <h.rei...@thelounge.net>
> 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 ma
On 10/10/2015 10:28 AM, Richard Reina wrote:
If I were keeping tract of high school sports statistics and thus designed
the following tables:
sports, rules, statistical definitions
and
players, teams, games
Would it be a good or bad idea to put the first set of tables in a separate
If I were keeping tract of high school sports statistics and thus designed
the following tables:
sports, rules, statistical definitions
and
players, teams, games
Would it be a good or bad idea to put the first set of tables in a separate
database called "library" since they are used for
I would lean towards keeping it all together because of the speed
decrease between connecting to different databases.
What I would tend to do is put some type of prefix that would keep the
sets of tables together --- like
lib_sports
lib_rules
lib_statistical
lib_definitions
data_players
Am 10.10.2015 um 16:28 schrieb Richard Reina:
If I were keeping tract of high school sports statistics and thus designed
the following tables:
sports, rules, statistical definitions
and
players, teams, games
Would it be a good or bad idea to put the first set of tables in a separate
When I read the OP I was thinking: This is one for Reindl. And here we
go.
When dealing with data of this specific kind, you most definitely
would want a date reference. A very small computer will be able to
handle
mane years of all kinds of weird sports statistics.
You need to define the
