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

Consider using UUID primary key instead of secondary index #124

Open

a3kov opened this issue May 16, 2017 · 2 comments

a3kov commented May 16, 2017

Need to evaluate the option of using UUID primary key everywhere.

Author

a3kov commented May 16, 2017

Pros:

ability to refer entities in distributed systems
ability to prepare data for conflict-free insertion
no need to depend on serial id in heterogeneous systems
saving storage space because UUID will replace redundant serial pk

Cons:

I've read that many years ago some DB engines could not implement UUID/GUID primary key index efficiently. However for modern engines this could be no longer the case. Need to check this, especially for proprietary engines such as Oracle and MS SQL Server

Author

a3kov commented May 20, 2017

Perf. optimization that could be a good idea also (haven't check its usefullness yet):
https://groups.google.com/d/msg/sqlalchemy/uq3xPCmAmN8/YgMNQ6KGBgAJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment