Hmm the documentation doesn't explain how I should proceed with an entity
object.
Is it enough to close the connection in the entity object and let the
framework open/close the connection for me?
In constructor:
MyEntities myEntities = new MyEntities(connectionString);
In each thread:
myEntities.Connection.Open();
Do stuff, including transactions...
myEntities.Connection.Close();
Or should I create/dispose whole entity objects instead (and the connection
with it)?
In each thread:
MyEntities myEntities = new MyEntities(connectionString);
Do stuff, including transactions...
myEntities.Dispose();
I guess the latter as it would probably get its own connection object, but I
am not quite sure here (ADO.NET might do connection sharing).
--
Bernhard
-----Original Message-----
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Joe Mistachkin
Sent: 20. juli 2012 23:00
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] System.Data.SQLite, Linq, multithread and transaction
usage
The basic thread-safety rules of System.Data.SQLite are documented here:
https://system.data.sqlite.org/index.html/artifact?ci=trunk&filename=Doc/Ext
ra/limitations.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
