[sqlite] disk I/O error...?

Hello I am getting disk I/O error with: [a...@search1 align]$ du -hs T.3.sqlite 122MT.3.sqlite [a...@search1 align]$ sqlite3 T.3.sqlite SQLite version 3.6.6 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .schema CREATE TABLE trigrams (w1,w2,w3,occs); CREATE

Re: [sqlite] disk I/O error...?

You'll get this if you have a database with an active journal (incomplete transactions) and you don't have write access to the database. In other words, the database needs a rollback from some prior operations done under a different userid, but now you don't have write access to do the rollback.

[sqlite] step() fails with SQLITE_BUSY after BEGIN EXCLUSIVE TRANSACTION

Hi, I'm using the latest amalgation of sqlite on Windows NTFS, compiled with SQLITE_THREADSAFE=1, from Visual C++. I have two threads which update a database. Each thread uses sqlite_open_v2 to open a connection. Both threads do essentially this: if BEGIN EXCLUSIVE TRANSACTION successful

Re: [sqlite] disk I/O error...?

Hello. On Sat, Apr 11, 2009 at 3:04 PM, Jim Wilcoxson wrote: > You'll get this if you have a database with an active journal > (incomplete transactions) and you don't have write access to the > database.  In other words, the database needs a rollback from some > prior

[sqlite] Heuristics of when to vacuum

Hello, I'm sure this question has been asked before, but I haven't been able to find it in the archives: when does it make sense to vacuum? If an application which deals with a large database vacuums say, on termination, it may take a long time to process them and not gain much from that

Re: [sqlite] "extension-functions.c" in windows mobile

On Fri, Apr 10, 2009 at 3:40 AM, Jay A. Kreibich wrote: > On Thu, Apr 09, 2009 at 04:34:53PM +0200, Thibaut Gheysen scratched on the > wall: > >> I have found the "extension-functions.c" in the >> contrib page of the SQLite website but I'm not able to build it for windows >> ce.

Re: [sqlite] step() fails with SQLITE_BUSY after BEGIN EXCLUSIVE TRANSACTION

Wow this sounds exactly like my post of a few days ago titled "Strange sqlite_busy deadlock behavior". On Sat, Apr 11, 2009 at 7:11 AM, wrote: > Hi, > > I'm using the latest amalgation of sqlite on Windows NTFS, compiled with > SQLITE_THREADSAFE=1, from Visual C++. > > I have

Re: [sqlite] step() fails with SQLITE_BUSY after BEGIN EXCLUSIVETRANSACTION

Hi, Dave I have read your post. I have also read many of the recent archived posts, and googled the web for hints. I'm at a loss here. The fun thing is that my wrapper class (which I use for a while now in non-MT environments) allows me to track most of what's going on in SQLite. And even that

[sqlite] Multiple connections from different threads

Sorry for asking such a basic question, and it seems I know the answer but I would like a confirmation. If I am executing the same SQL statement from multiple database handles to the same database file, I still need to prepare a distinct sqlite3_stmt for each connection, even though the SQL

Re: [sqlite] Multiple connections from different threads

On Sat, Apr 11, 2009 at 8:58 PM, Vinnie wrote: > > Sorry for asking such a basic question, and it seems I know the answer but I > would like a confirmation. > > If I am executing the same SQL statement from multiple database handles to > the same database file, I still need

Re: [sqlite] Heuristics of when to vacuum

Sent from my iPod On Apr 11, 2009, at 10:40, Tito Ciuro wrote: > Hello, > > I'm sure this question has been asked before, but I haven't been able > to find it in the archives: when does it make sense to vacuum? If an > application which deals with a large database vacuums say,

Re: [sqlite] Heuristics of when to vacuum

Hi Lawrence, On Apr 11, 2009, at 7:51 PM, Lawrence Gold wrote: > I can't offer a formula, but I suggest making it an option for the > users of the software, with sufficient warning that it could take some > time, as well as a Cancel button. Another thing you could do is to > schedule the vacuum