> On Oct 24, 2017, at 8:14 AM, Arno Gramatke wrote:
>
> My first naive approach was to figure out, which commands will result in a
> read and which will result in a write to the db file.
I think you’ll need to assume that any SQLite access can both read and write
the
Have you run "PRAGMA integrity_check;" from the command line shell against the
same database and does it return rows or just throw the same exception?
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original
On 24 Oct 2017, at 4:03pm, Roberts, Barry (FINTL) wrote:
> Our system would get a list of the rowid problems allowing it to log them and
> inform the user. I am currently testing using the 1.0.105.1 driver, however
> the ExecuteReader() call (above) throws an exception
On 24 Oct 2017, at 4:14pm, Arno Gramatke wrote:
> These single files should be placed in the app’s „Documents“ folder, making
> them accessible from other apps or the Files.app when allowed by the user.
> With the single db file from above it was only ever our app to
Hi all,
in an iOS app we have been storing multiple user „documents“ (hierarchical data
mostly, but some larger blobs (~2MB) as well) in a single data base file, that
was stored in the app’s "Application Support“ folder. That has worked without
problems so far.
Since iOS 11 we would like to
Hi,
I asked the following question a few weeks ago, but did not get any responses,
hoping someone may have an idea.
We are currently running System.Data.SQLite.dll 1.0.80.0 and would like to
upgrade to a newer version. However there are a variety of issues we have run
into, most of which I
6 matches
Mail list logo