On Tue, Mar 16, 2010 at 4:44 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> One of the things that makes SQLite very simple is that it doesn't try to do
> this, it has either everything or nothing locked.
Yes, that is coming to realization n
n and read_uncommitted set to 1. If you don't use shared
> cache and turned off locking on VFS level then you can easily get
> database corruption.
> On Tue, Mar 16, 2010 at 2:12 PM, HLS <sant9...@gmail.com> wrote:
>> Thanks Simon. It just seem so simplistic
or even been looking at the feasibility of changing code
(which is the last thing I don't want to do.)
On Tue, Mar 16, 2010 at 1:31 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> On 16 Mar 2010, at 5:17pm, HLS wrote:
>> Once approach is to queue any updates/deletes when the databas
On Tue, Mar 16, 2010 at 1:01 PM, HLS <sant9...@gmail.com> wrote:
> dim f as TFileRecord
> dim tid as integer
> dim n as integer = 0
> if GetFirstFileRec(FileNameAreaKey, f, tid) then
> ... do something ...
ssible writing while readers
> are active right away. Beware though that if you have open reading
> cursor and trying to write over the same SQLite connection then your
> transaction won't be committed until cursor is closed.
> On Tue, Mar 16, 2010 at 11:36 AM,
On Tue, Mar 16, 2010 at 11:54 AM, Olaf Schmidt <s...@online.de> wrote:
> "HLS" <sant9...@gmail.com> schrieb im
>> ...we have a ISAM/BTREE database under our full
my application to boost its performance).
> On Tue, Mar 16, 2010 at 10:05 AM, HLS <sant9...@gmail.com> wrote:
>> I read the documentation suggesting to use another SQL engine for a
>> multi-threaded client/server environment an
er process will be
allowed access to the database because I am going to open it in none
sharing more. All access will be through the client API.
So how do I make it so there is no locking?
sqlite-users mailing list
Mail list logo