premesh
03-06-03, 14:59
| So im having some trouble designing a database i want to use. here is an example of my object design [a] - abstract class int ID_NUMBER String NAME [a.1] extends [a] abstract class [a.2] extends [a] abstract class [b] extends [a.1] abstract class [c] extends [a.1] abstract class [d] extends [b] [e] extends [b] . . . [h] extends [b[ so i have this tree type object design in which they all have an ID and a name... and ultaimatly a type . at first we had a table with a list of ID's names and "types" being some character that represented a type ( could possibly be looked up in some sort of a typeCode table") but since every object has a string of type associated with is it seems messy to store a bunch of tables just to m ap each object ( instance of) to its type.. example u have a instance of type e... then u know its also of type b and not c as well as type a.1 and not a.2 ... is there a good source to look for as far as books or documentation to map these objects to database tables well? |