Join GitHub today
Attach encrypted database results in Out of Memory Error #1799
Using the latest nightly build on Windows 10 (also happening with the release build!)
I have two encrypted databases (same key).
I open the first database, then attach the second database.
If I try to execute any SQL that includes any tables in the attached database I'm getting an Out Of Memory Error.
If I try to browse any of the attached tables - at the bottom of the screen where row count should appear it says "determining count of rows..."
If I try the following "PRAGMA integrity_check;" I get an Out Of Memory Error.
If I execute "DETACH DATABASE database_name" then everything returns to normal.
...and I assume opening the second database and performing an integrity check also comes back clean?
The latest build now allows me to Attach a database however
Am also now getting a new error when trying to detach the database using
The error is (database name is import)
Execution finished with errors.
Hmm, there is something really messed up around Attach and the issuing 'detach database name'
UPDATE: - The folllowing only SOMETIMES works.
However if I do the following
If I don't do (2) first then any other sql seems to generate the Out Of Memory error...
Note - Am now going through the outstanding GitHub Notifications I've been mostly ignoring for the past 2 weeks, prior to building the 3.11.2 release binaries. I have a feeling this issue might be a release blocker.