Skip to content
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

Cancelling queries #33

Open
lana-k opened this issue Apr 10, 2021 · 3 comments
Open

Cancelling queries #33

lana-k opened this issue Apr 10, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@lana-k
Copy link
Owner

lana-k commented Apr 10, 2021

No description provided.

@lana-k lana-k added the enhancement New feature or request label Apr 10, 2021
@twoxfh
Copy link
Contributor

twoxfh commented Jun 17, 2021

Any thoughts around this @lana-k ? Would really like to recover from the accidental large query.

@lana-k
Copy link
Owner Author

lana-k commented Jun 17, 2021

@twoxfh the problem here is when you terminate a web worker you lose your database. At least it is how I see it for now. Of course, we could warn the user like "if you cancel the query you will have to load your database again". But for me it is undesirable. So I want to make some research or something in order to find the best solution for this.

@twoxfh
Copy link
Contributor

twoxfh commented Jun 21, 2021

I submitted an issue to sql-js, which has a very convoluted solution. As recognized in that issue, having an additional thread to call the interrupt really is the answer but likely not worth the effort at this point until greater browser compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants