database design - MD5 hash as artificial keys -


i'm seeing lots of applications using hashes surrogate keys instead of plain integers. can't see reason kind of design.

given uuid implementations hashed timestamps, why many database designers choose them application-wide surrogate keys?

if data backend application made out of multiple distributed databases, using incremented integer ids might lead duplicated values. uuids guaranteed unique not inside application outside (which might helpful when joining external data).

it true using different id seeds different databases in system solve uniqueness problem integers, managing such approach more difficult.


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

aspxgridview - Devexpress grid - header filter does not work if column is initially hidden -

c# - How to execute a particular part of code asynchronously in a class -