Hey,

2012/8/26 Offirmo <offirmo....@gmail.com>:
> Hello all,
>
> I'm still working on my Wt app and who knows, maybe I'll have something
> to show you one day ?
>
> But for the moment, I'm stuck with this error :
> [error] "Wt: error during event handling: Sqlite3: insert into
> ""real_user"" (""version"", ""email"", ""creation_date"",
> ""last_modif_date"", ""sti_type"", ""denomination"") values (?, ?, ?, ?,
> ?, ?): database is locked"
> [error] "Wt: fatal error: Sqlite3: insert into ""real_user""
> (""version"", ""email"", ""creation_date"", ""last_modif_date"",
> ""sti_type"", ""denomination"") values (?, ?, ?, ?, ?, ?): database is
> locked"

That is truly odd. What kind of system is this, and did you build
Sqlite3 seperately, and if so, what version of Sqlite3 and with what
compile options ?

I can only imagine that somehow your Sqlite3 version is not multi-thread safe ?

>      // then add it to db
>      {
>          // again, in its own transaction
>          Wt::Dbo::Transaction transaction(dbo_session);
>          element_ptr = dbo_session.add(p);
>          transaction.commit();
>      }

Wt::Dbo deals with transactions in the following way: if there is
already a database-transaction open, it will simply join this
database-transaction, and otherwise it will start a new
database-transaction.

In neither case you can get this database-locked error since
everything happens using the same SQLite3 connection.

Regards,
koen

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to