Of course, but I'm wondering if the overhead of an extra index on inserts is worth it; I guess having a unique single ID for each enrolment is still a Good Thing(tm). The amount of data is so small that it the extra index will probably make little difference to inserts.
-----Original Message----- From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Sent: Wednesday, 1 June 2005 11:25 To: CF-Talk Subject: Re: (SOT) Joins aren't always better than subqueries (longish post) James Holmes wrote: > Yes, I found that out the hard way (bad data import). I'll drop the > existing PK and create a composite key. You don't have to drop the existing PK. Just add another unique index. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208221 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
