feat(core): ground work for query cancellation + PostgreSQL implementation. #1484
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
commit: |
igalklebanov
force-pushed
the
cancelation-p1
branch
from
a3d18c9 to
627be4a
Compare
igalklebanov
added
enhancement
igalklebanov
force-pushed
the
cancelation-p1
branch
from
cbd6804 to
5e75c61
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
5e75c61 to
10d619b
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
d51f3a3 to
98dd794
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
9f663a3 to
521e2e3
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
6f22429 to
ee130c9
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
ee130c9 to
a4db0d3
Compare
igalklebanov
commented
Jul 28, 2025
There was a problem hiding this comment.
The names were conflicting with the general QueryOptions this PR introduces.
igalklebanov
force-pushed
the
cancelation-p1
branch
from
a4db0d3 to
0525eea
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
0525eea to
4b3dc8f
Compare
igalklebanov
force-pushed
the
next
branch
2 times, most recently
from
f13491f to
90d6c71
Compare
igalklebanov
force-pushed
the
next
branch
2 times, most recently
from
f3c3650 to
9adaf87
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
4b3dc8f to
98e862b
Compare
|
@igalklebanov is attempting to deploy a commit to the Kysely Team Team on Vercel. A member of the Team first needs to authorize it. |
igalklebanov
force-pushed
the
cancelation-p1
branch
2 times, most recently
from
e143120 to
f852fa6
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
f852fa6 to
0ea15e5
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
2 times, most recently
from
364747d to
3ecc532
Compare
apply executable @ select. test suite prep. ?? best bench results. ... update qb. merge qb. insert qb. delete qb. kysely. raw builder. fix regression in takeFirst. more core. abort. ... ... ... ... ... ... ... ... ... executeQuery. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
igalklebanov
force-pushed
the
cancelation-p1
branch
from
3ecc532 to
70da7fc
Compare
igalklebanov
force-pushed
the
cancelation-p1
branch
from
cab8d72 to
285a816
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hey 👋
part of #783
This PR sets the foundations for dialects to implement query cancellation.
An
executable<O>interface is created and all relevant builders implement it.All
executeandstreamfunction accept an options object that might includesignal.This
signalis passed down to the executor, and handled there.The connection receives a hint at query time that it might need to prepare itself for cancelation - e.g. in PostgreSQL you need to make a request to get the
pidof the connection.The connection has a
cancelQuerymethod that, in dialects that support it, cancel the query on the database side.Verifying this works with PostgreSQL.