name conflicts in rdbms

How do I represent OOPL packages and nested classes in an RDBMS?

Consider these packages and classes:

[my.package::MyClass]

[my.package.subpackage::MyClass]

[my.package.subpackage::MyClass.MyClass]

Here are four diffrent classes, and I want to represent them all in my RDBMS. Major nameconflicts.

I could of course represent each package as a unique database, since packages are there to encapulate a piece of the system. But from experience I know there will be some associations between the packages -- and I don't want relations between multiple databases if I don't have to.

But it still don't help me with the nested class. I could name the tables with the full classpath, but many RDBMS:es have a limited table name size (Oracle 8i, PostgreSQL, et.c) making it virtually impossible.

The only solution I can see is to give each class a unqiue pre/suffix, but that doesn't make it human eye friendly-- something I demand.

Any thoughts on this?

karl Received on Tue Apr 29 2003 - 03:20:08 CEST