Date: Sat, 24 Jan 2009 16:23:26 +0000
I'm currently working on a system that consists of several sites. Each site runs a system with its own local database, and then periodically each site updates the "master" site with its data, allow the data to be viewed centrally.
It must be done like this because each site may not always be on the network, but the data must always be available from the central server.
To enable the master database to contain all the site database information, I use a composite key, with the first part being the site identification, and the second part being the row identification. This allows user with row id 5 for instance to exist more than once because paired with the site id it is still unique.
On top of this, there is another layer. Each site must be contained within an "Enterprise", which is just another identifier. So, I have a table called enterprise which contains the list of site ids.
So far then, I have this (obviously cut down to only show the relevant columns) : -
column: site_id column: id column: label
With the site_id and id making the composite key.
Now, I've just had to add the concept of "enterprise" level users. Initially the only clean way I could think of doing this is having two separate user tables; enterprise_user and site_user : -
However this does not seem very "normalized"..
Other ways I considered are : -
But this does not make sense as an enterprise user is not associated with any site. I could have a dummy site, but I really do not like that. I could just set site_id to NULL, but I'm not a big fan of NULL in database and it just seems a bit hacky.
So then I thought of adding a link table:
table: user_site <== link table
column: enterprise_id column: user_id column: site_id
with a unique constraint on enterprise_id, user_id (the composite key that identifies a user in an enterprise).
I think that also works.. basically with no entry in the "user_site" table, they are enterprise users. An entry in user_site effectively limits them to being a site user.
However.. this might create complications in the "master" update process.
Part of the batch update process involves updating user information. Enterprise users (only editable at the master) must be propagated down to each site, so that the site is "aware" of enterprise users.
Site users (only editable at the site) must be propagated up to the master, purely so all the (read only) data at the master is complete.
So I'm wondering if having the two tables separate will be just much simpler (although not being terribly efficient in terms of pretty much repeating a table structure).
I hope all that makes sense!
Mark. Received on Sat Jan 24 2009 - 10:23:26 CST