I do not yet have one that reproduces the problem outside of our
application. I will try and see if I can come up with one.
On 1 May 2012 12:48, Joe Mistachkin <sql...@mistachkin.com> wrote:
>
> Greg Carter wrote:
> >
> > I tried out the changes on the tkt-996d13cd87 br
Hi Joe,
I tried out the changes on the tkt-996d13cd87 branch and our application
runs fine with pooling on, at least for the test case that I was using to
reproduce it within our app.
Thanks!
On 30 April 2012 15:28, Joe Mistachkin wrote:
>
> Alexander Spence wrote:
> >
>
On 27 April 2012 11:39, Larry Brasfield wrote:
>
> When you use a collection of native code from managed code, and when that
> native code has cleanup to do, defined by its own conventions rather than
> the conventions established for the managed code system, you
We recently upgraded to 1.0.80.0 from 1.0.77.0 and have found when we turn
connection pooling on we get seemingly random memory access violations that
happen in calls to UnsafeNativeMethods.sqlite3_busy_timeout ,call stack -
Open/SetTimeout (line 259 of SQLite3.cs).
After compiling SQLite debug
4 matches
Mail list logo