Skip to content

[Feature Request] Support for sqlite3_interrupt #545

Description

@troygibb

Hey sql.js maintainers! Thanks so much for this great software, we've been getting great milage out of it!

It sounds like it's possible to add sqlite3_interrupt support based on your discussion in #461, it just hasn't been prioritized. We've implemented the suggested workaround of killing and re-instantiating the worker, but obviously it would be a lot more performant if we surgically interrupted queries.

Is this feature on your radar? Any idea of how much work it would involve? Thanks in advance!

Activity

kaizhu256 commented on Feb 27, 2023

@kaizhu256
Member
  • unlikely to be on radar soon.
  • sqlite3_interrupt() requires opening a secondary database-connection in a secondary thread to interrupt the first thread
  • web-workers are single-threaded -- there's no easy way to [asynchronously] open a secondary database-connection to it and call sqlite3_interrupt().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions