The way I interpret Ben's article, he has a leaning towards using identity style primary keys.
I think Ben is saying he leans towards DB specific coding to take advantage of whatever databases enterprise features -- and in this specifies using identities specific to each dbtype. His statement about CreateUUID() is to my mind ridiculous -- but perhaps the article puts it out of context.
It's what I run with for some fairly complex db designs, and I've found them easy, convenient and effective.
I suspect that these designs using identity would not easily migrate from one DB to another, nor would the data have any hope of being migrated from one DB platform to another (without the use of migration scripts etc). However, dbtype migration is not really an issue for most.
I'm not entirely sure why UUIDs as keys would have any sort of impact at all on db design. The only impact I can see is with data storage and index efficiency -- but then I'm not really a DBA.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
