-
Notifications
You must be signed in to change notification settings - Fork 2
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
UUID as entry_id ? #15
Labels
discuss
help wanted
Extra attention is needed
question
Further information is requested
starter
technical
Comments
nelsonic
added
help wanted
Extra attention is needed
question
Further information is requested
discuss
starter
technical
labels
Nov 1, 2018
This was referenced Nov 2, 2018
Open
This was referenced Jan 9, 2019
Open
Thanks for this phenomenal append-only log example! PostgreSQL has a UUID type that only takes up 16 bytes (much less than UUID as string) and is supported by Ecto: Migration: add :entry_id, :uuid Schema: field :entry_id, Ecto.UUID Was string chosen for UUID storage for a particular reason? |
@njwest thanks for sharing. I hadn’t spotted the PgSQL UUID Type. Good to know. 👍🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
discuss
help wanted
Extra attention is needed
question
Further information is requested
starter
technical
At present we are using a Random UUID for
entry_id
see: /lib/alog.ex#L269
This is good in that it is "globally unique".
But is it the most effective unique ID we could be using?
The text was updated successfully, but these errors were encountered: