Skip to content

Conversation

rkistner
Copy link
Contributor

@rkistner rkistner commented Apr 3, 2024

Fixes #36.

Also improves handling of database initialization errors and other uncaught errors in connection isolates.

The new test currently often fails with this error:

SqliteException(261): while executing, database is locked, database is locked (code 261)
    Causing statement: PRAGMA synchronous = NORMAL, parameters: 

It is likely caused by opening multiple connections at the same time. #34 will fix the issue.

@rkistner
Copy link
Contributor Author

rkistner commented Apr 4, 2024

Closing in favor of #38, which builds on this PR. The "closing database" tests are still unstable on this version (even though it's way better than before), while it appears to be completely fixed in #38.

@rkistner rkistner closed this Apr 4, 2024
@rkistner rkistner deleted the fix-closing branch April 4, 2024 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Closed Exception when the SqliteDatabase.close is invoked
1 participant