Neither would I throw stones at anyone, but remember that dynamic table identifiers can be an issue on some RDMS (for instance; Oracle table names cannot exceed 30 characters).
This problem can easily be avoided with validation code, but in your case, I would strongly advocate using the DBMS schema functionality as well. On Mon, May 4, 2009 at 18:55, <[email protected]> wrote: > > Not that I am throwing stones, but you really should raise an issue about > this schema design. I perviously worked in a company that took this approach > in designing their data model. As you have already seen, this is not an easy > data model to work with for obvious reasons, but the greatest problem with > this design is the fact that you are intermingling different companies data. > How do you think General Motors would feel knowing that their data resided > in tables right next to Ford's. I'm certain Ford would not like this as > well. You should leverage the database's schema functionality to isolate the > data properly. >
