I am struggling with a design issue. I am working on a new project, a server application that receives a request and then renders CAD drawings from engineering specs stored in a database. I am designing a SQL 2005 database that will be the management database for the new application.
I have the concept of a drawing... a SubmittalDrawing to be specfic, which has a collection of revisions. Then, I need to extend both objects and have specific implementations... ProjectDrawing, QuoteDrawing, OrderDrawing, etc. Should I define the one to many relationship on what will ultimately be the base classes... or on the specific classes... or both?
SubmittalDrawing
UID
PreparedBy
Voltage
Drawing
SubmittalDrawingRevision
UID
SubmittalDrawingUID
RevisedBy
RevisedDate
RevisionNumber
Drawing
