> On 26 Sep 2017, at 12:14 am, Clemens Ladisch <clem...@ladisch.de> wrote:
>
> Roberts, Barry (FINTL) wrote:
>> As per my original post, all C# access code is making extensive use of
>> "using" statements. However we do obviously rely on the connection pool
>> being thread safe, because many threads are writing to different
>> databases (connections) concurrently.
>>
>> There is no direct relationship between threads and databases. However
>> I do enforce that within a process only one thread can be writing to
>> a specific database (because sqlite does not support parallel writing)
>> at a time.
>
> How exactly are you enforcing that?
>
>> public IDbConnection CreateConnection()
>> {
>> var connection = new SQLiteConnection
>> {
>> ConnectionString = m_Builder.ConnectionString
>> };
>>
>> return connection;
>> }
>
> I would be tempted to replace that ConnectionString variable with the
> actual connection object, and not using the connection pool. (Assuming
> that the builder objects are not shared, or properly locked.)
>
>
> Regards,
> Clemens
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
