Re: Tables in a database

Mark Fisher wrote: > > Thanks for replying. Unfortunately the tables are being forced upon us by > the application: Business Objects. B.O. creates a repository that handles > the users security etc. and we cannot control the structure, but each > universe repository needs to have its own set of tables. I may have to > rethink whether we will allow 2 repositories which would remove the need > for multiples on the same d.b. > > The contractors who are in helping us set up the repository just keep > saying *really* useful things like "You wouldn't have this problem with > Oracle" or "You can do that on Oracle". I bite my tongue. As Nils would say " Shit Shit Shit Shit!":-) I would say in good ol' american slang, THis is BULLSHIT! (Sorry if I offended the PG-13 crowd.) What you are saying is that one must create a table for each instance of an OBJECT? In this case a user? That is totally incorrect and I'd bitch slap the authors of such a program. In concept, you would need to create a single repository. If you have multiple users, then user_id would have to be a field of the tables, rather than a separate table for each user. Ask your pathetic consultants if they have ever heard of normalizing their data? Or what it really sounds like is that this tool was written for a single user (PC) environment and then placed on a UNIX box and claimed to be multi-user! HTH -Mikey -- #include <std_disclaimer.h> /* Mike Segel (MS385) */ #include <No_Spam.h> #ifdef OFFENDED_BY_CONTENT The author takes no responsibility for this post. Any resemblence to a coherent rational thought is purely coincidence. -The Management. #endif ***************************** Due to AGIS's Refusal to Act Responsibly We are blocking all of their domains at the packet level. This block will exist until AGIS modifies their policies to conform to existing RFCs and net community standards. We encourage all ISPs and domain holders to do the same. *****************************