Simon,
no, i don't think this can help. because my problem is busy handler was not
triggered at the situation.
Another reply is from Mr. Hipp ! I believe it must work, because he is the
god here :-)
thank you anyway.
2011/8/11 Simon Slavin slav...@bigfraud.org
On 11 Aug 2011, at 3:35am, Wenbo
Hi guys,
I want a readonly connection wait for locked database instead of error
return immediately.
The question is equivalence to how to let a reaonly connection have
busy_handler triggered
when the database is locked.
In my practice, the readonly connection will fail when db locked and
with such a basic question. I'm still new in SQLite.
Pavel
On Sun, Sep 20, 2009 at 2:04 AM, Wenbo Zhao zha...@gmail.com wrote:
I was talking about this example by
2009/9/19 Igor Tandetnik itandet...@mvps.org
Imagine the
classic example, where a transaction first verifies that the balance
for
transaction that _made_ any reads, 'write lock' - for transaction that
_made_ any writes.
Pavel
On Sat, Sep 19, 2009 at 12:18 AM, Wenbo Zhao zha...@gmail.com wrote:
This is not a good example i think.
If a transaction is intent to update after the select, it should start
a write
This is not a good example i think.
If a transaction is intent to update after the select, it should start
a write lock before the select.
And as described in previous 'dead lock' example, the update in this
example could fail due to 'dead lock'
I believe the 'read lock' is designed for a 'read
i can't see the attachment
why don't you use the sqlite-amalgamation*.zip ? that's very easy to compile
2009/9/14 TEZ sqli...@tezukuri.hobby-site.org
make test became faild. What's wrong?
I tried with sqlite-3.6.17.tar.gz and sqlite-3.6.18.tar.gz, but both
packages
failed by running make
with 25 left outer joins.
If your objects and queries are simple, there's no harm in coding the
database access by hand.
- Original Message -
From: Wenbo Zhao zha...@gmail.com
To: sqlite-users@sqlite.org
Sent: Thursday, September 10, 2009 8:12 PM
Subject: [sqlite] looking
Hi, all
I have been looking for a simple and practical solution of Object/Relation
Mapping over JDBC
to use with sqlite. I think this should be a common problem for all users
who write app with
sqlite in java.
On the net, it seems everybody is talking about Hibernate in this field.
I'm new in
