Thanks Joe.
I fetched the latest leaf code with INTEROP_LEGACY_CLOSE and am now getting
ready to build it.
Looks like I have to flip the switch in SQLite.NET.Settings.targets and
SQLite.Interop.20XX.[vs]props to enable the functionality. Is this correct?
- - - Philip
________________________________________
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Joe Mistachkin [sql...@mistachkin.com]
Sent: Thursday, February 14, 2013 8:40 PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] Change in behavior between 1.0.79.0 and 1.0.83.0 in
System.Data.SQLite
Mason, Philip wrote:
>
> What operation(s) are creating these?
>
It looks like pretty much any query against the database.
>
> Are the objects/connections actually orphaned or is there the possibility
> that activity could pop up and cause problems?
>
Yes, I confirmed that the objects are actually orphaned.
>
> If the pre-sqlite_close_v2 code in 1.0.81.0 will solve the issue safely,
> I'd like to explore the option of fetching the old code and moving forward
> that direction.
>
An alternative to using older versions of System.Data.SQLite would be to
compile
it with the new compile-time option INTEROP_LEGACY_CLOSE enabled:
https://system.data.sqlite.org/index.html/timeline?r=legacyClose
--
Joe Mistachkin
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
