Hi, Thanks for the information. Just to confirm that implementation, I am returning SQLITE_OK for the functions sqlite3OsLock sqlite3OsUnlock
and the function sqlite3OsCheckReservedLock returns 0 assuming that the file has not reserved locks. Please advice if this is Ok. With regards, Sankara Narayanan B "D. Richard Hipp" <[EMAIL PROTECTED]> 2004-08-18 06:09 PM Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: [sqlite] FileLocks - help requied [EMAIL PROTECTED] wrote: > Hi, > > I am currently porting sqlite 3.0 into my device application. The device > is running on an ARM7TDMI processor. The filesystem available on device is > Nucleus file system. > > For this file system I am not sure whether I have the file locking > mechanisms as provided in Sqlite 3.0. But the advantageous situation I > have is only one thread in the application will be accessing SQLite all > time (all the sqlite interfaces are protected using semaphores and there > will be no two threads simultaenously accessing sqlite at any time). > > For this requirement how do I implement my OS functions sqlite3OsLock and > sqlite3OsUnlock? Is it possible to work with no locking mechanism? I find > that the lock utilisation (in pager.c) is not available with switches. > Please advice me on how I could modify the sqlite code accordingly. > If only one thread or process is accessing the database at a time, then no locking is required. -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
