I've been following along, so I've already seen this message.
What operation(s) are creating these?
Are the objects/connections actually orphaned or is there the possibility that
activity could pop up and cause problems?
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.
- - - Philip
________________________________________
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Joe Mistachkin [sql...@mistachkin.com]
Sent: Wednesday, February 13, 2013 7:11 PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] Change in behavior between 1.0.79.0 and1.0.83.0in
System.Data.SQLite
Mason, Philip wrote:
>
> Joe mentioned that there seemed to be orphaned SQLiteCommand objects that
appear
> to be keeping the connection open, is this correct? What part or
function of
> the Entity Framework or System.Data.SQLite are generating these?
>
Some details here:
http://www.mail-archive.com/sqlite-users%40sqlite.org/msg74770.html
--
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
