Re: [sqlite] Database sharing across processes

Thanks, Pavel, for answering my questions! >> I am also thinking that I may want to make use of the sqlite_unlock_notify() >> call to ensure that if I try to write to the database and it fails to get a >> lock, it will pend until it is available. However, I thought that a query >> would

Re: [sqlite] Database sharing across processes

On Saturday 07 July 2012 01:00:01 Jonathan Haws wrote: > For example, let's say I have two processes that connect to the same > database file. One process wants to read from the database, but the other > process is in the middle of a write. Does the first process pend on the > read or not? If

Re: [sqlite] Database sharing across processes

On 6 Jul 2012, at 4:00pm, Jonathan Haws wrote: > So, then what is the best way to make a query from one process pend until the > database is available? > > For example, let's say I have two processes that connect to the same database > file. One process wants to

[sqlite] Linux "managed only" issue(?)

Hi I have been meaning to port my .net2.0 project to Linux for years and at last done and working (kind of.. testing on Mono 2.6.7.5 on Debian 6) Now the issue. I am using 1.0.66.0 System.Data.SQLite.dll in my project and in Windows everything runs fine Using the same .66 but the managed

Re: [sqlite] Linux "managed only" issue(?)

Dave Edwards wrote: > > For Linux I have recompiled the managed only dll from the .081 source > using: build.bat ReleaseManagedOnly (so no need for the interlop.dll to > be placed in the root folder) > And I have had to mod the built.bat so it runs: >%_AECHO% Forcing the use of the .NET

[sqlite] Understanding Foreign Key Contraints

I have a fairly complex web based application which helps manage the process of running an American Football results picking competition through the season. I am in the process of porting it to Sqlite ready for the start of next season. I just discovered a bug in my handling of a constraint

Re: [sqlite] Linux "managed only" issue(?)

On 07/07/2012 17:28, Joe Mistachkin wrote: Dave Edwards wrote: For Linux I have recompiled the managed only dll from the .081 source using: build.bat ReleaseManagedOnly (so no need for the interlop.dll to be placed in the root folder) And I have had to mod the built.bat so it runs: %_AECHO%

Re: [sqlite] Linux "managed only" issue(?)

Dave Edwards wrote: > > Still exactly the same issue though in Linux , around 300 rows imported > and it falls over. I wonder if it is thread related then? If it is then > I will have remove support on Linux as the app is multi-threaded and as > far as I was concerned thread safe (never

[sqlite] using SQLITE_BUSY

In http://ideone.com/7lhIh is my example code. I would like to know if this would be an appropiate implemetation/use of BEGIN IMMEDIATE and sqlite3_busy_timeout. As I understood from the documentation and literature about Transaction and locks the sqlite3_step is the action state part so I

Re: [sqlite] Linux "managed only" issue(?)

Joe Mistachkin wrote: How was the native SQLite library compiled? Was it compiled with SQLITE_THREADSAFE set to 1? Also see: https://www.sqlite.org/threadsafe.html Compiled in Debian build proc I suppose with the default of 1. I am trying to find the source file :) I will try a few

Re: [sqlite] Linux "managed only" issue(?)

Dave Edwards wrote: > > Anyone know of any bugs with Mono 2.6 or debian 6 that could cause this > as it might be there rather than here I should be looking? > I seem to recall that System.Data.SQLite does not work correctly on Mono less than about 2.8; however, I'm not exactly sure why. --