Skip to content
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.

Sign up for GitHub

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

Jump to bottom

using random_create instead of timestamp_create #7

Open
mlsquires opened this issue Jan 29, 2012 · 2 comments
Open

using random_create instead of timestamp_create #7

mlsquires opened this issue Jan 29, 2012 · 2 comments

Comments

@mlsquires
Copy link

I'd prefer to use the type 4 UUID (random). Any thoughts about supporting this? I should have mentioned in the other issue that I'm happy to code up a solution for either of these if they don't fit in your roadmap.
@pnegri
Copy link

pnegri commented Jun 25, 2012

v4 UUIDs isnt secure as v1 and should be only used in partial solutions (Like a table where you are going to have a compound id, for example, a timeline (user_id + timeline_uuid).

@ivanoblomov
Copy link
Contributor

Have you tried SecureRandom.uuid?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pnegri @mlsquires @ivanoblomov