Hi Folks,
Please forgive me if this isn't the proper forum to post this question
but I am in need of some expert advice concerning if SQLite is the best
choice for my application.
Our application could have up to 10,000 users via a public facing web
site. As a first stab at the schema, I thought I'd have one "Master
User" database which will probably look like this:
*Master DB *- (would contain contact info for all of the "Users")
user_ID - PRIMARY KEY
last_name
first_name
email
street_addr1
street_addr2
city
state
zip
date_signed_up
date_to_renew
username
password
If I use SQLite, there would be another database that contains user
setup data that describes the various different ways that their page
would be displayed, each user could have up to 100 "subjects"and then
each "subject" could have 10-25 "events". So this database could look
like this:
*User DB* - each user gets one of these that includes 3 tables
(user_setup, subjects, events)
TABLE_USER_SETUP
user_id (FOREIGN KEY)
setup_id
data1
data2
data3
data4
TABLE_SUBJECTS
subject_id PRIMARY KEY
last_name
first_name
email
street_addr1
street_addr2
city
state
zip
password
TABLE_EVENTS
events_id PRIMARY KEY
type
data
subject_id
Can I use the user_id (as a FOREIGN KEY) that resides in another
database to link the two DBs together? I'm a newbie to all of theis
database design so I am using this project as a learning experience.
From my limited knowledge of MySQL I think I could have everything in
one database and just have a bunch of tables. If I use SQLite I'd have
a bunch of files (or smaller databases). If there was a problem I can
see just losing one ueser's data and not the whole "ball" of data with
all the user's data.
You folks are the experts and I'd like to hear what you recommend.
Thanks,
Richard
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
