Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

1
Suggestion for ID strategy
Author Summary
alekslyse is in Idaho
Post Body

I have beed made software for decades, but I have never done performance testing for ID vs UUID. I am designing a pretty large C# project, and automatically I always used an int ID in the database, and IDs for relationships, but I have been wondering if it would be safer to use UUID?

I was initially thinking to keep the auto inc integer ID for internal operations, then UUID for any requested interaction, but still having an ID I would assume _could_ in edge cases where for example a DTO mistakenly keeps an ID to be open to guessing an ID.

So in 2024, whats the most accepted approach.

  1. Keep both an ID and GUID, refer to ID internally, and UID externally

  2. Ditch the int ID and use GUID as primary key

  3. Other?

Author
Account Strength
90%
Account Age
9 years
Verified Email
Yes
Verified Flair
No
Total Karma
1,261
Link Karma
561
Comment Karma
700
Profile updated: 7 months ago
Posts updated: 4 hours ago

Subreddit

Post Details

Location
We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
4 days ago