>>> [EMAIL PROTECTED] 12/15/03 09:00PM >>> > ** Note that if you have a base class for a generic "thing" and extend > it for specific "thing"s, you might not really have persistence for the > base class. If ArticleBO is generic, you probably don't have ArticleBO > instances so you *probably* don't need an ArticleDAO since there won't > be anything to persist!
So it seems that if the parent class has no instances, and you store 2 subclasses in the same table (e.g ARTICLE) or if you have all of the subclass properties (including those in ArticleBO.cfc) in separate tables (e.g. JOURNAL_ARTICLE and WEB_ARTICLE, with no ARTICLE table), then you might not want to have an ArticleDAO.cfc. If you chose to implement the persistence with ARTICLE, JOURNAL_ARTICLE, and WEB_ARTICLE tables, where ARTICLE stores the properties in ArticleBO.cfc, would you not want to have an ArticleDAO.cfc to save the data that is specific to the ArticleBO.cfc? Then, JournalArticleManager.CreateJournalArticle() would call ArticleDAO.Create() and JournalArticleDAO.Create(). Similarly, WebArticleManager.CreateWebArticle() would call ArticleDAO.Create() and WebArticleDAO.Create(). Otherwise, you would have to twice code the DB logic for the data that is common to JournalArticleBO.cfc and WebArticleBO.cfc. Does that sound right? Jon ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
