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

refactor API to be more consistent with other ulid implementations #1

Open
rmalayter opened this issue Jul 5, 2017 · 0 comments
Open

Comments

@rmalayter
Copy link
Owner

rmalayter commented Jul 5, 2017

Right now the dbo.ulid() function returns a UNIQUEIDENTIFIER type, while in ULID implementations for most other languages ulid() returns the string version of a ULID. Refactor API of this implementation to be more consistent with others. It might be best to not have a "bare" dbo.ulid() function at all, and instead always include a "type" as part of the function name for clarity, e.g. dbo.ulidMSSQL() would return the MSSQL-sort-friendly specific format UNIQUEIDENTIFIER, and dbo.ulidChar() would return a CHAR(26) BASE32-encoded version. Add conversion functions as well.

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

1 participant