Hello!
I think your structure is not good enough. You may use
cookie-based database selection instead and doesn't
store user information into your "Master DB".
The algorithm is like to:
Username -> user_id -> check password by user_id database
As example:
User enter USERNAME and PASSWORD and we
On Sat, 6 Mar 2010, Richard Cooke wrote:
> 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:
Richard,
If I recall correctly, SQLite does not do well
Richard Cooke wrote:
> 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 everyt
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 thou
4 matches
Mail list logo
