Ķaмȋļ ๏ Şκaļşκȋ
kamil.skalski at gmail.com
Mon Jul 14 14:42:07 EDT 2008
Still, you need to use separate connection for each thread - it should
be a perfect use of
On Sat, Jul 5, 2008 at 12:34 PM, Angel Marin <anmar at anmar.eu.org> wrote:
> Anders Aagaard wrote:
>> Every thread has it's own cloned SqliteConnection (during the creation of
>> the thread I call MasterConnection.Clone (), and only use the referenced
>> connection). The exception happens instantly when two threads begin a
>> transaction to the same database.
> Last time I had to use sqlite on a multi-threaded environment tweaking
> the busy_timeout connection string parameter did the trick. From mono docs:
> 'The busy_timeout parameter is implemented as a call to
> sqlite(3)_busy_timeout. The default value is 0, which means to throw a
> SqliteBusyException immediately if the database is locked.'
> Though sadly there doesn't seem to be a similar parameter on 2.0 profile
> sqlite assembly.
> Angel Marin
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list