objectbox / objectbox/objectbox-java
UUIDs as object identifiers (maybe string based?)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.6k
- Forks
- 311
- PR merge metrics
- No merged PRs in 30d
Description
I know that there are some tickets around, but honestly, its quite annoying to not have this key feature of a database implemented. I saw, that there were some efforts in 2017 (thats 4 years ago btw.) but nothing changed since. So instead of only having Long as an id primary type, i also would like to have String and UUID. I know, that there are maybe some performance impacts with that, but that should not matter, since its the responsibility of the developer to choose the correct id types.
Use case scenario for UUIDs:
Distributed systems, where you identify your entity by its globally unique UUID, and you dont want to deal with internal system ids and the global UUID.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing primary-key and object-identifier support, then locate the earlier tickets and 2017 efforts referenced in the issue. The scope needs to establish how String and UUID identifiers should work and what compatibility or performance constraints apply. Done should include agreed behavior and coverage for both identifier types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100