Re: [sqlite] When to close a db, take 2...

and will not call sqlite3_close. Unless the second thread is called between the copy and the null assignment. I think that these concurrent accesses should be protected by a critical section. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 (Ext.133) Fax +34

Re: [sqlite] SQLJet - pure Java implementation of SQLite

and kicking and highly portable: http://www.freepascal.org Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 (Ext.133) Fax +34 93 5883007 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi

Re: [sqlite] How to build sqlite rpm package

distribution site for instructions on how to build an rpm (e.g, for mandriva it is at http://wiki.mandriva.com/en/Development/Howto/RPM) Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007

Re: [sqlite] wrong # of entries in index occur in MultiThread insert operation

, you shouldn't hijack an existing thread for a new topic, use the Compose or New button in your mail program, hitting Reply then changing the subject will still show your message in the original thread in any well behaved mailer. Bye -- Luca Olivetti Wetron Automatización S.A. http

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

En/na Luca Olivetti ha escrit: En/na Dennis Cote ha escrit: The original corruption may well have been caused by omitting the thread safe option on the version of SQLite you were using. Pheew, I hope it is really so. A quick follow-up: everything has been working fine for almost one month

Re: [sqlite] corrupt db vacuums clean on 3.2.7 but not 3.5.4 or 3.5.6

with 3.3.8 (and, as you say, 3.2.7) it appeared to work. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi

Re: [sqlite] Newbie question re using SQLite in basic client/server situation

En/na Jeff Brown ha escrit: But I need to be able to use it as a server with at most 10 clients that occasionally use the system. Hi, I'm a newbie myself, so I didn't use the following, but did you check http://www.sqlite.org/cvstrac/wiki?p=SqliteNetwork ? Bye -- Luca Olivetti Wetron

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

En/na Dennis Cote ha escrit: Luca Olivetti wrote: Well, I posted all the error messages I got back from sqlite, as well as the snippet of code I use to execute all my queries, but I can post more details if it can be useful (I'd only need to know which details could be). Ah, I'm sorry

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

En/na Luca Olivetti ha escrit: I don't believe that there is any reason to expect a vacuum to correct a corrupt database. Ah, ok, I thought that it did (at least it did with 3.3.8). Side note: it wasn't actually completely corrupted (hard corruption came after), or at least I think

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

En/na Luca Olivetti ha escrit: En/na Luca Olivetti ha escrit: Hello, I'm using sqlite 3.3.8 under linux (mandriva 2007.1). [...] 1) is sqlite suitable when you have multiple threads accessing the same database? Or should I delegate the access in a single thread and serialize

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

be useful (I'd only need to know which details could be). Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

En/na Luca Olivetti ha escrit: En/na Luca Olivetti ha escrit: Hello, I'm using sqlite 3.3.8 under linux (mandriva 2007.1). [...] 1) is sqlite suitable when you have multiple threads accessing the same database? Or should I delegate the access in a single thread and serialize

[sqlite] vacuum doesn't clean all errors with 3.5.6, it did under 3.3.8

integrity_check; wrong # of entries in index fifo_referencias wrong # of entries in index sqlite_autoindex_fifo_fis_1 Is this expected? If so, how can I fix these errors? (yes, I know that I could dump and restore, but I need something more automated). Bye -- Luca Olivetti Wetron Automatización S.A. http

Re: [sqlite] Can I manually Lock a database?

En/na Jerry Krinock ha escrit: How can I manually lock the database using the C API? I can't find any lock function. In think you could just execute a BEGIN EXCLUSIVE query, then do your thing then execute a COMMIT (or a ROLLBACK if something failed). Bye -- Luca Olivetti Wetron

Re: [sqlite] How to recover from database corruption? (and why does it happen?)

En/na Luca Olivetti ha escrit: Hello, I'm using sqlite 3.3.8 under linux (mandriva 2007.1). [...] 1) is sqlite suitable when you have multiple threads accessing the same database? Or should I delegate the access in a single thread and serialize the queries from the various threads? 2

[sqlite] How to recover from database corruption? (and why does it happen?)

; If FSQLiteReturnId=SQLITE_CORRUPT then begin FLog.Error('intento un VACUUM'); if Vacuum then FLog.Info('VACUUM ok'); end; end; end; until finished; sqlite3_finalize(vm); end; TIA Bye -- Luca Olivetti Wetron