On 11/14/05, Seth Johnson (KW) <[EMAIL PROTECTED]> wrote: > But since the StatementID is only a persistence mechanism, and has no > "business use" other than uniquely identifying a database row, does it > belong in the Statement object?
Yes. The StatementID uniquely idenitfies a statement. You could use it to compare two statement objects to see if they represent the same statement. It's probably useful in several contexts. There may be another way to uniquely identify a statement by combining two or more fields. If that's the case you probably have a "candidate key" in your database that your DAO could use. But introducing a single unique identifier would probably do no harm and make lots of people's lives easier. Patrick -- Patrick McElhaney 704.560.9117 http://pmcelhaney.weblogs.us ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] 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/[email protected]
