Stephen Russell wrote:
> Use the same db for multiple retail stores for the tires store. If your
> using ints your going to be screwed or have a LOT of code rewrite on your
> hand
>
>
>
I thought about that. The solutions could be :
1. use another integer field in each table called iClientID for each
client, and have all SQLs respect the Client ID they're working with
2. use GUIDs, but still come up with a way to not have one client's
data showing for a different client (see option #1!)
3. use separate databases for each client
I like #3 because it's kinda like not putting all of your eggs in one
basket, and as more sites come on board, there's no risk to anyone else,
especially if any client wants customizations that are extra or even
contrary to the previous clients. No risk of busting other clients!
Plus, I can move their database easily without having to extract it from
the "mega-database" that has all kinds of customers in it. Plus-plus, I
can more easily backup and restore their data, as again, I don't have to
mingle with other clients databases. Besides, the tools exist today to
update one database structure from another, so it's not like I'm
recreating from scratch everytime. I simply copy the structure and I'm
good to go for the next new client.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
