>> Actually what I do more frequently nowdays is use >> createUUID() to generate a primary key of my own >> and insert that instead of using identity fields. >> All of these issues go away then.
> That's a good idea, except that UUIDs take more > space and are slower to index when compared to > integers. However, that's only a problem if you > are dealing with large amounts of data. It only starts to become an issue with tens of millions of records, at which point you have bigger issues than indexing a 32 character string instead of an integer. It's also a vanishing issue as hardware and database evolution diminish it over time. Some of the other issues related to large data sets, most notably usability issues are not diminished over time by hardware or human evolution. s. isaac dealey 434.293.6201 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.fusiontap.com http://coldfusion.sys-con.com/author/4806Dealey.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236963 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
