1
vote
What is a good strategy to avoid creating duplicate profiles for many individuals in a database?
Strategy 1 swaps one risk (leaking a private id) to another (leaking other private information, e.g. that a given person is a customer + request history). The attacker just needs to guess a customer ...
1
vote
What is a good strategy to avoid creating duplicate profiles for many individuals in a database?
Ok, I will try to make a shot in the dark - your question seems to miss some information, but let me see how far I can get from what you wrote.
I think it is safe to assume customers are real persons, ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
database × 2163database-design × 458
design × 226
sql × 199
architecture × 182
relational-database × 164
mysql × 140
c# × 108
design-patterns × 94
java × 81
php × 77
nosql × 77
web-applications × 74
web-development × 69
data × 68
data-structures × 65
performance × 63
sql-server × 60
orm × 55
microservices × 53
postgres × 51
object-oriented × 47
algorithms × 47
api × 44
security × 43