[Mono-list] Single .dll targeted at multi platform but using sqlite, possible?

[KeithBoynton]

A tiny bit of progress (I think)...

Adding "BusyTimeout=100" to the connection string changed the exception to
this:

LockFileEx  at (wrapper managed-to-native)
Community.CsharpSqlite.Sqlite3/LockingStrategy:LockFileEx
(intptr,uint,uint,uint,uint,System.Threading.NativeOverlapped&)
  at Community.CsharpSqlite.Sqlite3+LockingStrategy.SharedLockFile
(Community.CsharpSqlite.sqlite3_file pFile, Int64 offset, Int64 length)
[0x00000] in <filename unknown>:0 
  at Community.CsharpSqlite.Sqlite3.getReadLock
(Community.CsharpSqlite.sqlite3_file pFile) [0x00000] in <filename
unknown>:0 
...
  at Community.CsharpSqlite.SQLiteClient.SqliteCommand.ExecuteReader
(CommandBehavior behavior) [0x00000] in <filename unknown>:0 
  at Community.CsharpSqlite.SQLiteClient.SqliteCommand.ExecuteReader ()
[0x00000] in <filename unknown>:0 
  at Community.CsharpSqlite.SQLiteClient.SqliteCommand.ExecuteScalar ()
[0x00000] in <filename unknown>:0 
  at SoundHound.DatabaseManager.ExecuteScalar (System.String sql) [0x00000]
in <filename unknown>:0 
  at SoundHound.DataAccessManager.InitialiseDataStore () [0x00000] in
<filename unknown>:0


I've removed some of the stack trace so this thread is not too messy.
There's some strange locking issue going on in MacOS that doesn't happen in
Windows. I may try to compile the community DLLs on mono macos to see if it
helps....



--
View this message in context: http://mono.1490590.n4.nabble.com/Single-dll-targeted-at-multi-platform-but-using-sqlite-possible-tp4656335p4656376.html
Sent from the Mono - General mailing list archive at Nabble.com.