The performance issues mentioned give me another opportunity to defend my idea of an INT primary key and a GUID candidate key. :-) <cfbeat obj="deadhorse">If your db has to support sometimes-connected apps (for which GUIDs are best suited) you'll have the GUID field to use, but for operations within the db and in always-connected apps you'll want to use the INT. The latter will not only save weight in the generated HTML (my original point), it'll be more efficient on the db side.</cfbeat> ---------------------------------------------------------- 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]
