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.

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

Add Support for ULID #284

Open
tiagoandrepro opened this issue Oct 28, 2024 · 2 comments
Open

Add Support for ULID #284

tiagoandrepro opened this issue Oct 28, 2024 · 2 comments

Comments

@tiagoandrepro
Copy link

Currently, DrawDB does not offer support for ULID (Universally Unique Lexicographically Sortable Identifier). This limits performance optimization opportunities when working with databases that require efficient indexing and lexicographic sorting. UUIDs, while functional, can lead to slower queries and less efficient data management.

I would like to see ULID support added to DrawDB. ULIDs maintain the same uniqueness guarantees as UUIDs but improve query performance by being sortable. This feature would enhance the overall efficiency of database management, especially in scenarios with large datasets.

Adding ULID support would align with DrawDB’s commitment to efficiency and modern development practices, improving the experience for developers.

@sudhirVoid
Copy link
Contributor

That is really a nice input @tiagoandrepro . I will like to proceed with this one.

@HeCorr
Copy link
Contributor

HeCorr commented Feb 2, 2025

@tiagoandrepro In theory you could store a ULID value in a UUID column since they have the same size I think (but you need to store it's binary data, not the string format with dashes). If not, you could probably store it as bytes.

Adding a ULID data type to DrawDB would only make sense if your database supports the ULID data type (natively or via a plugin) ,i.e. CREATE TABLE users (id ULID PRIMARY KEY, ...);.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@tiagoandrepro @sudhirVoid @HeCorr and others