jay1891

Hi, if I may ask, is something as @EricBos suggests going to be implemented?

I shall try to see if I can get the SQL string. With SQLite version 1.1.14 it ran for months and it didn't occur. We are now only upgrading to...

Yesterday a LoggerFactory was set on the DbContextOptionsBuilder, so we could log the SQL statements, as shown below. It ran all day without any exception. Today I removed the LoggerFactory...

As attachment below I added a little description of the application. [Application description.pdf](https://github.com/ericsink/SQLitePCL.raw/files/3984892/Application.description.pdf) Is this helpful?

_So once per second you insert one row? Each row in a separate transaction?_ => In normal operations and during which also the exception occurs, there are currently +-80 rows/second...

Yesterday I did a little test with the NullLoggerFactory and the exception also occurs.

Thank you for the information Eric. Because I could not use the attributes on an async method I am now testing with the following approach which was also referenced in...

After adding `` in the app.config, and removing the LoggerFactory, I could capture the actual data (MessageHistory rows) that is added to the DbContext and being saved by SaveChangesAsync(). The...

I wrote the following test for the MessageHistory.json file which contains the messages on which the exception occurs in the application, but the exception is not occuring in the test....

To clarify the (test) code a little: The DbContext is encapsulated inside a wrapping entity repository (class) in which the DbContext is injected and on which some basic operations are...