Any recommendations on the preferred way to handle this scenario:
I have a class Folder that is a collection of objects that derive from a "Document" base. In the old architecture, the FolderItem table had columns to store both a class ID and an identity for the Document that comprised that item. So when the Folder was instantiated, the collection would read each FolderItem and then, based on the class ID, go get the right object, which could be one of several different classes, each stored in a different table. Thus in the database the FolderItem's "DocumentID" column isn't a foreign key to a single table.
What's the best practice for implementing this in LLBLGen? Reproduce the same logic in the generated classes, or add a column to the FolderItem table for each kind of document it could store? For example, instead of DocumentClassID and DocumentID columns, FolderItem would have DocumentKind1ID, DocumentKind2ID, DocumentKind3ID, etc., with only one of them populated, based on what kind of document was being held.
