Dave, I wouldn't want a "Document" array as the file can be associated with any other item in the DB (hence the Join table with foreign tables/keys). But, by that respect, would it be reasonable to have a FileBean object that has an Associations collection and the following methods:
+ AddAssociation( ForeignTable, ForeignKey ) + RemoveAssociation( ForeignTable, ForeignKey ) So then my form processing logic would be: - Create document bean - Set form data into document bean - Commit document bean data - Create file bean (via upload via FileController) - Add the document to the file bean associaitons - Commit the file bean data Does that look ok? Thanks, ...................... Ben Nadel Web Developer Nylon Technology 6 West 14th Street New York, NY 10011 212.691.1134 212.691.3477 fax www.nylontechnology.com Programming is my "money" job. My real passion is eating. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Ross Sent: Monday, February 13, 2006 2:46 PM To: CFCDev@cfczone.org Subject: Re: [CFCDev] CRUD (plus?) the File object should have an array of document ID's. Your FileDAO would create the associations during a save (create/update). You can split that out into separate functions if you wish, but they should be private and only called from within the DAO. Helps? -Dave ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
