-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 regression tests for sqlite explain #2180
Conversation
Problem: PgHasArrayType was checking the application's postgres feature Solution: only check the library's postgres feature Co-authored-by: Daniel Tashjian <daniel@ecomedes.com>
* add failing test cases for update/delete return into * fix regression in null tracking by improving tracking of cursor empty/full state * add failing test case for order by column types * Add support for SorterOpen,SorterInsert,SorterData * add failing test case for unions * fix range copy/move implementation * fix wrong copy/move range * remove calls to dbg!
…chbadge#1946) * add instruction, register, and cursor state memorization * fix: fixed formating
* feat: Add set_connect_options method to Pool This allows external updates of the ConnectionOptions used when a new connection needs to be opened for the pool. The primary use case is to support dynamically updated (read: rotated) credentials used by systems like AWS RDS. * Use Arc wrapper for ConnectOptions to reduce lock contention * sqlite fix * Use direct assignment instead of mem::swap Co-authored-by: Austin Bonander <austin.bonander@gmail.com> Co-authored-by: Austin Bonander <austin.bonander@gmail.com>
* AggValue and ROW_NUMBER() * Some more functions * cargo fmt
…iness is different (launchbadge#2120)
Some opcodes for reference
|
Just as a heads up, you may want to base your pull request off of the "0.7-dev" branch instead of main. Changes to type-inference are delayed until the next minor version, rather than a bugfix release. And there is at least one fix for 'order by' type inference in that branch already. |
@tyrelr well, it seems to be fixed in 0.7-dev. That's great news. |
1f285a7
to
3961dc3
Compare
@0rvar can you rebase? |
@abonander I now have capacity to rebase this, if you're still interested. Let me know |
Original: Fix SQLx+Sqlite incorrectly inferring column as nullable when using ORDER BY and LIMIT in the same query
Status: added a failing test, reading through the opcode state machine in
explain
.Tips and ideas are appreciated.
Related:
Option
NULLable-types #1852Semi-related:
std::option::Option
#1294It seems the original issue was already fixed in 0.7-dev.
I changed this PR to add more tests for the issues in 0.6 if they are of interest - otherwise, feel free to just close this.