On Mon, 18 Oct 2004 14:53:41 -0500, Norland, Martin <martin.norland@xxxxxxxxxx> wrote: > That all really depends on you. I would certainly say that, in general, > any given database should only have one users table (with a separate > table holding roles, permissions, etc.) In all likelihood - if all of > these systems will be working together within a single company, and be > built in a common way - you'll likely find it easier to have them all in > one system. > > The counter to that, of course, is that information like payroll > certainly shouldn't be easily accessed - so that might be one case where > you might want a separate database. You'll really just have to weigh > the benefits of having the data together (generally convenience, though > there are reasons along the lines of joins and such) with the costs of > any lost security or lax in responsibility. shouldn't a good rdbms take care of that though (with reasonable security measures)? can't you get fine grained user privs, at least with a proper db? postgres? Cheers Antoine -- G System, The Evolving GUniverse - http://www.g-system.at -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
