I’m trying to use the Sqlite nugget package in a test assembly.
I’m getting the following error in my app when running a query in code:
{System.DllNotFoundException: Unable to load DLL 'sqlite3': This operation is
only valid in the context of an app container. (Exception from HRESULT:
0x8007109
On 2/21/18, Deon Brewis wrote:
> I do.
>
> I'll have to request permission from the customer though to share it - who
> will potentially be looking at the file? (Just so I can share names and
> background with the customer to put him at ease).
You can send corrupt database files (and correspondin
I do.
I'll have to request permission from the customer though to share it - who will
potentially be looking at the file? (Just so I can share names and background
with the customer to put him at ease).
- Deon
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailingl
> On Feb 21, 2018, at 7:45 AM, Simon Slavin wrote:
>
> My concern was that it's abnormal for "sqlite3LeaveMutexAndCloseZombie" to
> take five seconds to execute.
As of a few weeks ago, I know all about this function ;-) It's called when the
last statement is closed on a "zombie" database con
On 21 Feb 2018, at 3:34pm, Deon Brewis wrote:
> Yes, definitely the main thread - we close down the database during
> applicationWillTerminate. It gives us 5 seconds to exit before it triggers
> the watchdog.
Okay, that all sounds right, and the dump you pasted suggested everything
worked rig
That number doesn't surprise me. At my company, one of our products is
built around iPads. Airlines give their pilots 16-32GB iPads to bring into
the cockpit to look at maps, charts, weather info, etc. The iPads
essentially become EFB, or, Electronic Flight Bags. Compressed, we push
two or thre
Yes, definitely the main thread - we close down the database during
applicationWillTerminate. It gives us 5 seconds to exit before it triggers the
watchdog.
Termination Description: SPRINGBOARD, process-exit watchdog transgression: xxx
exhausted real (wall clock) time allowance of 5.00 seconds
On 21 Feb 2018, at 2:35pm, Deon Brewis wrote:
> The application got watchdog terminated by iOS because the main thread was
> taking too long (waiting for the sqlite3close on the worker thread). The
> resultant force close seems to have aborted SQLITE in such a way that it
> caused the database
On 2/21/18, Deon Brewis wrote:
>
> a) Is it expected that an app crash / force terminate in the middle of a
> SQLITE3 checkpoint like this can cause corruption?
No. See, for example, https://www.sqlite.org/atomiccommit.html and
https://www.sqlite.org/wal.html and . If the filesystem is behaving
Interesting case of database corruption on iOS here.
Our main thread was waiting for a worker thread to exit. The worker thread was
doing a sqlite3Close, which in turn did a checkpoint.
The application got watchdog terminated by iOS because the main thread was
taking too long (waiting for the s
On 02/21/2018 05:56 PM, Matthew Dumbleton wrote:
Hi sqlite users,
Can you help me with this problem?
I have switched a long standing project from using whatever version of sqlite
is on the device to include the aar file generated by the android bindings
project. However since the change over I
Hi sqlite users,
Can you help me with this problem?
I have switched a long standing project from using whatever version of sqlite
is on the device to include the aar file generated by the android bindings
project. However since the change over I get an 'unknown error (code 14): could
not open d
Further to the earlier replies, here is a funny SQLite demo of function,
keyword, and column names that is informative about the possibilities.
sqlite> .load distinct.so
sqlite> SELECT DISTINCT "distinct"() "distinct" WHERE [distinct] NOT NULL;
distinct
"fn distinct was called"
distinct.c ext
13 matches
Mail list logo
