Re: [sqlite] search time is non-determinate in multi-thread enviroment

On Jul 28, 2009, at 8:09 PM, pierr wrote: > http://www.sqlite.org/threadsafe.html > "Multi-thread. In this mode, SQLite can be safely used by multiple > threads > provided that no single database connection is used simulataneously > in two > or more threads." > > If I have one(different) conne

Re: [sqlite] sqlite3_blob_read problem with buffer in Objective C

On Apr 14, 2009, at 12:48 PM, Richard Dauben wrote: > After successfully reading from a blob sequentially to a buffer in > Objective C > the buffer seems to be altered such that it can no longer be > accessed from > memory Is there some kind of special buffer type that I should > be usi

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, on > termination,

Re: [sqlite] Strange sqlite_busy deadlock behavior

On Apr 8, 2009, at 3:12 PM, Dave Brown wrote: > Thread A is in the process of executing sqlite3_step(). I can post the > full stack if you want. It goes all the way down to winSleep() in the > sqlite3 codebase. After the full busy timeout, thread B (not A) gets > SQLITE_BUSY returned. Does each t

Re: [sqlite] sqlite3 --version showing the wrong version

On Mar 19, 2009, at 5:19 PM, erfon haubenstock wrote: > > ok so macports installed sqlite3 just fine, but how do i check the > version? > i think i now have 3 versions of sqlite installed. > > 1 - when i type sqlite3 --version i get version 3.4.0 > 2 - when i type usr/local/bin/sqlite3 --version

Re: [sqlite] sqlite3 --version showing the wrong version

On Mar 19, 2009, at 4:29 PM, erfon haubenstock wrote: > > Hi again. Thanks for trying to help me by the way : D > > I tried relauching terminal and even restarting my computer, but to no > avail. > > I'm not totally sure I understand when you say: > > One common pitfall here is that you must open

Re: [sqlite] sqlite Btree

On Jan 15, 2009, at 4:54 PM, Alex Krzos wrote: > It is not specified anywhere, but is the sqlite btree a b+tree. I > noticed > that pages with in the btree source file have the ability to be > identified > as either leaf or leafdata does this mean that sqlite uses a b+tree? I recall reading

Re: [sqlite] Multithreaded vs. serialized

On Jan 14, 2009, at 4:07 PM, John Belli wrote: > Assuming I've decided to use evil threads, and am opening a new > connection in each thread, does it matter whether I use multithreaded > (-DSQLITE_THREADSAFE=2) or serialized (-DSQLITE_THREADSAFE=1)? Any > idea if one is faster than the other? I am

Re: [sqlite] Question about concurrency

(Apologies if this doesn't end up in the correct message thread.) > In CONFIG_MULTITHREAD mode, you are responsible for serializing calls > on a single database handle and its statement handles yourself. If you > make calls on a single database handle from two or more threads > simultaneously > th

[sqlite] Question about concurrency

This question may sound a bit daft, but I'll ask anyway: If I use SQLite in the default SQLITE_CONFIG_SERIALIZED threading mode and share a connection among threads, does that connection support multiple simultaneous reads, or will each read access be serialized? I'm assuming that for maximum conc

[sqlite] Using Sqlite in place of BDB

Hello, I work for a company which is seeking to replace its homegrown database engine with a more robust, modern engine. I've looked at BerkeleyDB, which would be ideal since all we really need are key/ value pairs for our records and indexes, but its cost is rather prohibitive. At this p