Devart Forums

Hello,

any new insights with this problem?

Best regard
Hans

This is correct behavior (DB locking on calling DROP), that is described in the SQLite documentation http://www.sqlite.org/c3ref/unlock_notify.html .

OK, this I handled meanwhile.

But I thought on the main theme of this topic: the difference between 32bit and 64bit compilation: In 32bit the thread runs fine, in 64bit not.

best regards
Hans

Please try to compose a small x64 test application and send it to support*devart*com.

I did so twice

Unfortunately, we haven't received any your message at support*devart*com . Please try to upload the test project to a file exchange service and share the download link with us.

OK, I do so and try to update the test program before so that all my trials to get that running under 64bit are up to date.
I'll post it on my ftp site and send you the URL to download, making a new entry here. Maybe it lasts 2-3 days till I'm ready.

best regards
Hans

Hello,

ready.
You can download the demo with this link:
http://www.lhsoft.de/DevartDemoSQLLite.zip
about 40MB, 3 databases, 2 of them are large.

Follow the instruction in the memo.

32bit runs fine without any error, tested up to 24 hours.

64bit will fail after a while:
if, with 64bit, the fail lasts too long, restart, so the error may come sooner or copy file "1 Complete.NEU" from subdirectory "Imports" to the work directory so 217000 datasets are imported at once and not only 10000.

While testing now, I got a new error message: "unique constraint failed: KaLagKas2.Idx", but this is defined as

[Idx] INTEGER PRIMARY KEY AUTOINCREMENT

Sometimes there is a error message like: invalid file or encrypted database.
Maybe this 2 messages are first steps for corruption.

best regards
Hans

Did you now get the demo and can you reproduce the error?
best regards
Hans

We continue investigation of possible reasons for such behavior. We will inform your the results shortly