On Sat, Oct 3, 2009 at 4:02 PM, John Meyer <john.l.meyer@stripped> wrote:
>> Thanks. The data is private to each user; there is no sharing of data. I
>> am not sure what you mean by "are the actions related" Each user is
>> reading/writing independently of each other. Would that argue for separate
> Are the actions of a similar nature (i.e. they're all writing the same type
> of data and the databases themselves would be similar if not the same)?
Each user will write the same type of data to the same schema. So the
databases schemas would be identical.
Is there any sort of application that would traverse all of those databases
> at once?
Not really necessary from the user's perspective.
Also keep in mind that multiple databases increases your complexity. I
> think we'd have a better idea if we knew a little more of the specifics of
> this application.
Sure, no great military secrets here. The application is a mobile softball
(baseball, basketball, soccer, etc.) score book. The data for each pitch
(softball = pitch type, who made what play, what the batter did, errors,
etc.) is entered on the cell phone, and stored in MySQL tables in order to
create game and season stats for a team and each player. This can also apply
to other sports. Each user is a team manager or scorekeeper. There really
isn't any need for team A to see/access team B's stats. A league may want to
do a special type of roll-up, but this app is really just for each team. I
am sure an app could be written to do the roll-up, but that is not the main
I think by your discussion, it may make sense to have separate databases for
each user instead of add a userID column to many of the tables to separate
each user's data from the other users. Does that make sense?