Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposal to add
uuid()
functions as per source code here: https://www.sqlite.org/src/file?name=ext/misc/uuid.c&ci=tip. The documentation is updated, and simple tests are included. Localdevtools::test()
completed without errors.I trust that users will welcome to be able to generate
UUIDs
within the database, as this is performant and can be part ofSQL
logic (such as in my use case). There do not seem to be risks or unintended consequences (e.g., footprint, performance, security aspects).Possibly the same could be said about other extensions in the source repository; not sure if you plan for others to be included or a generic mechanism for compiling even with sources from outside the
SQLite
repository?Many thanks for considering!