SQLite isolation level

Thread is closed for posting
1 posts, 0 answers
  1. Lars
    Lars avatar
    11 posts
    Member since:
    Oct 2015

    Posted 21 Dec 2015 Link to this post


    due to my requirements my application should be able to access a SQLite DB in read-only mode through Telerik Data Access while the source application may still be writing to it (via native SQLite C++ API). It is sufficient if only those changes are visible to the application which were already commited at the time the DB connection was opened through the OpenAccessContext.

    I was assuming this could be done by setting the IsolationLevel to Snapshot. But it seems I'm missing something here. My attempt was to setup the writing code with standard auto-commit behaviour on each insert/update and set the OpenAccessContext to

      ContextOptions.IsolationLevel = System.Data.IsolationLevel.Snapshot

    However, this results in an exception, even when the database is not open anymore by the producer application:

    Telerik.OpenAccess.RT.Adonet2Generic.Impl.DBDriverException: Unsupported isolation level Snapshot


    Does my concept have any general flaw, is this simply nto supported by SQLite (I don't think so) or do I have toconfigure this differently for SQLite?


    Regards, Lars.


Back to Top