On 06/26/2013 02:08 PM, Woody Wu wrote:
On Tue, Jun 25, 2013 at 10:21:51PM -0400, Igor Tandetnik wrote:
On 6/25/2013 10:13 PM, Woody Wu wrote:
1. When a exclusive transation started and not yet commit, I found if I
open another connection to the same database and try to access it (using
sqlite3
On 26 Jun 2013, at 8:08am, Woody Wu wrote:
> Thanks for the analyzing. After checked, I found it's the prepare_v2
> statement, previous to the step statement, returned SQLITE_BUSY. That
> means, a prepare_v2 can even failure if the statement be preparing is an
> operation to an exclusive locke
On Tue, Jun 25, 2013 at 10:21:51PM -0400, Igor Tandetnik wrote:
> On 6/25/2013 10:13 PM, Woody Wu wrote:
> >1. When a exclusive transation started and not yet commit, I found if I
> >open another connection to the same database and try to access it (using
> >sqlite3_step), I got the error code SQLI
On 6/25/2013 10:13 PM, Woody Wu wrote:
1. When a exclusive transation started and not yet commit, I found if I
open another connection to the same database and try to access it (using
sqlite3_step), I got the error code SQLITE_MISUSE. It sounds a little
strange because I thought the error code s
Hi,
I have serveral questions about exclusive transaction. (version 3.7.x)
1. When a exclusive transation started and not yet commit, I found if I
open another connection to the same database and try to access it (using
sqlite3_step), I got the error code SQLITE_MISUSE. It sounds a little
strang
5 matches
Mail list logo