Replies: 1 comment
|
@Seyden This is likely a Swift issue and not a StructuredQueries one. Parameter packs are still not fully implemented and there are probably optimizations the compiler could make. If you can show more evidence that this is an issue with our library we'd be happy to take a look or any PR that fixes things, but I'm pretty sure you could reproduce this performance differential with parameter packs outside our library. For now I'm going to convert this to a discussion, since I'm not sure there's a ton that is actionable on our end. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
Hello,
I did play around with my queries locally and noticed that when I didn't fill my nullable string columns and afterwards selecting them, that the parsing time increases per each column by a lot.
After creating a benchmark test I noticed that this was only the case when wrapping the result set inside a tuple. I will post the benchmark code here and also the results.
Benchmark results
Code
Checklist
mainbranch of this package.Expected behavior
No response
Actual behavior
No response
Reproducing project
No response
Structured Queries version information
34453b5
Destination operating system
macOS
Xcode version information
Version 26.2 (17C52)
Swift Compiler version information
All reactions