nooooo!!! u guys dont understand. the state thing was an example! it was
a design issue in general, and i wanted a general answer. when is it good
to use and id, and when is it good not to. it's good to use an id if the
information changes a lot, but it could be sitll linked by ID, and can be
shared by many. but, if all of the many used textual of actual information,
instead of getting it from a common source, I'd have a lot of toruble going
through all of those rows just to change one thing. understand what i mean?
hehe
>From: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>To: CF-Talk <[EMAIL PROTECTED]>
>Subject: RE: Database design woes
>Date: Fri, 20 Jul 2001 14:22:59 -0500
>
>
>am i missing something?? isn't there something inherently wrong with using
>a state abbrv. as a primary key? as an index ok but primary key?
>uniqueness?
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
