-
-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to use UUIDs as primary keys #239
Comments
Thank you for your interest and feature request. When refactoring the project there were some considerations that lead to that decision.
We thought about implementing a "string id" feature but didn't have the time to do so. That said, If I remember correctly you can use the https://sleekdb.github.io/#/insert-data#updateOrInsert If you want to implement that feature you are welcome to do so 😊 The You could extract that into it's own class and allow the user to implement their own functionality by providing a closure, custom class using an interface or something like that as a configuration option when creating a Store-Object. Feel free to join our discord server if you need help or want to discuss details. |
Hi @Timu57, I certainly don't wat to introduce |
At this moment in time primary keys have to ne numeric:
The id of the document has to be numeric
I like to use https://github.com/ramsey/uuid to generate UUIDs for my entities, but I'm not able to use them as my primary key because they are not numeric. Is there a reason why there's such a restriction?
The text was updated successfully, but these errors were encountered: