Implement UNNEST in sqlite. Expose it via the postgres emulation. #383
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 PR adds
UNNESTwhich is an table valued function for zipping multipleRc<Vec<Value>>arrays together. Arrays are passed to sqlite using it's pointer passing interface. The array type accepted byUNNESTis the same which is accepted byrarrayinrusqlite.This makes it possible to make very efficient bulk queries in sqlite. For ex. bulk insertion:
or selecting/deleting a list of objects in a single statement:
This is very powerful as most patterns of
Can get converted to some sort of single statement using unnest.
I've exposed this feature on our Postgres emulation. Unfortunately due to some limitations array parameters need to be strongly typed and for now at most 10 array arguments per
unnestcall are supported. For now 4 array types are available via postgres -text[],blob[],int[]andfloat[].To use
UNNESTvia postgres make an explicit type cast, for ex:UNNESTis very efficient if there is significant network latency between the client and database.