[sqlite] affinity critical problem with 3.8.5 - IN single value optimisation

h a single value in the list on the right-hand side of the IN operator) as if they where "x==?", Similarly optimize "x NOT IN (?)"" Best regards, -- Guillaume FOUGNIES Eulerian Technologies ___ sqlite-users mailing list sqli

[sqlite] Virtual tables and locking.

hi, Is it possible to add some informations about locking mechanism in the wiki page VirtualTables? I'm facing concurrency problem in developing a cluster Sqlite database. One table per database. Multiple databases indexed like x.db, x.db-001, x.db-002, x.db-003, ... each containing a choosen

Re: Re[2]: [sqlite] how can i speed up inserts ?

re of corruption on crashes and power failures, you can modify sqlite to write your temporary '-journal' files in a ramfs mount directory. DB file: /opt/sqlite/mydb Journal in smtg like: /ramfs/opt#sqlite#mydb-journal -- Guillaume FOUGNIES Eulerian Technologies - To unsubscribe, send email to [EMAIL PROTECTED] -

[sqlite] Problems with threadsafe opt correction #2623

HECK_THREADID' in sqlite3OsLock and if the OsFile->tid eq 0, just call SET_THREADID. Bye, -- Guillaume FOUGNIES Eulerian Technologies

Re: [sqlite] Problems with threadsafe opt correction #2623

to 0. return the state. 1-bis: - "sqlite3_release" function. It checks the lock state of files. If something is locked, it releases transactions/file locks and finally set OsFile->tid to 0. 2: - Atomically, a thread try to 'CHECK_THREADID' in sqlite3OsLock and if the OsFile->tid eq 0, just

Re: [sqlite] Problems with threadsafe opt correction #2623

n this case, the ability of a handle to be used by more than one thread should be always denied to avoid portability problems. -- Guillaume FOUGNIES Eulerian Technologies

[sqlite] Re: (diff/patch) Problems with threadsafe opt correction #2623

not affected. > > > > The restriction that a DB handle can only be used from a single > thread is currently only enforced on Unix, because Unix boxes > are the only place where using DB handles in multiple threads is > a problem. -- Guillaume FOUGNIES Eulerian Techno

Re: [sqlite] Re: Thread safety guarantees

atabase handle. No. Each thread needs to open its own db handle and let SQLite make the lock job. That's all. Since you don't need a db handle opened by thread(a) to be used by another thread (b), you won't have any problem... If you need to, you will need my "lost patch" :) http://www.sqlite.org/cvstrac/tktview?tn=1417 -- Guillaume FOUGNIES

Re: [sqlite] Thread safe in 3.2.5

s out of sequence. I noticed there was a change in the > 3.2.4 version related to configuring the threadsafe operation that stated the > threadsafe option wasn't working. I don't understand why it was changed. I > haven't had any problems until now. Any help would be appreciated. > > Thanks, &

[sqlite] DEFAULT PAGE SIZE option = malformed database schema

Enter ".help" for instructions sqlite> pragma SQLITE_DEFAULT_PAGE_SIZE=16384; sqlite> .schema Error: malformed database schema Best regards, -- Guillaume FOUGNIES Eulerian Technologies 'I can't believe my eyes I must be dreaming, Wake up Jack, this isn't fair!' ~ Jack

Re: [sqlite] DEFAULT PAGE SIZE option = malformed database schema

5-09-19 at 19:04 +0200, Guillaume Fougnies wrote: > > > Hello, > > > > > > During the upgrade from 3.2.5 to 3.2.6, i removed my > > > compile time option SQLITE_DEFAULT_PAGE_SIZE. > > > > > > 3.2.6 is not able to access anymore to d

Re: [sqlite] Share an sqlite3 struct between multiple threads

y chance, yes, on some platforms. Recent versions of > SQLite explicitly disallow it and return an error if tried. > > Christian -- Guillaume FOUGNIES Eulerian Technologies

[sqlite] bug with progress handler and sql functions.

activate the progress handler. I've corrected the problem by adding a nProgressOpsI in the sqlite3 structure which increments properly despite many sqlite3VdbeExec calls. The patch is trivial. Bye. -- Guillaume FOUGNIES Eulerian Technologies

Re: [sqlite] Question about threads

embebbed OS and want to > >know how SQLite uses them. Each database will have its own thread or > >each part of SQLite (tokenizer, parser, btree...) have its own thread > >or a mixture of both? -- Guillaume FOUGNIES Eulerian Technologies

Re: [sqlite] Many bugs with threads (errors and corruption)

Fri, Jan 09, 2004 at 09:08:37AM -0500: D. Richard Hipp wrote: > Guillaume Fougnies wrote: > Probably the SQLITE_SCHEMA error is being incorrectly converted > into an SQLITE_ERROR somewhere as the call stack unwinds. I'll > fix it - but I consider this a minor problem. If you can gi

[sqlite] SQL Syntax from 2.8 to 3.0 not backward compatible?

Here is it: SQLite version 3.0.1 Enter ".help" for instructions sqlite> BEGIN TRANSACTION ON CONFLICT ROLLBACK; SQL error: near "ON": syntax error bye. -- Guillaume FOUGNIES - To unsubscribe, e

Re: [sqlite] SQL Syntax from 2.8 to 3.0 not backward compatible?

BEGIN cannot have an ON CONFLICT clause in sqlite > version 3. > > Dan. > > > --- Guillaume Fougnies <[EMAIL PROTECTED]> wrote: > > Here is it: > > > > SQLite version 3.0.1 > > Enter ".help" for instructions > > sqlite> BEGIN TRANSACT

[sqlite] problem on table create and synchronous in 3.0.1

src/pager.c:1548: syncJournal: Assertion `pPg->needSync==0' failed.Aborted -- Guillaume FOUGNIES - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[sqlite] 3.x pragma synchronous

Hello, PRAGMA default_synchronous disappeared from 3.x. Should we now execute a PRAGMA synchronous each time a db is opened? Could it be possible to get a configure flag or a define in sqliteInt.h to set this by default? Regards, -- Guillaume FOUGNIES

Re: [sqlite] 3.x pragma synchronous

off... during my tests, consequences are lots of busy timeout despite the same busy handler. I'm sad because concurrency and btree+ storage in 3.0 seems nicely improved, a great work as far as i can see. Fri, Jul 23, 2004 at 02:18:14PM -0400: D. Richard Hipp wrote: > Guillaume Fougnies wrote: > >

Re: [sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

rash using a journaling FS and incremental backups. If you want the speed and the fs sync, you probably need the hardware (less and less expensive). -- Guillaume FOUGNIES

Re: [sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

Tue, Sep 07, 2004 at 12:59:37PM +0100: Christian Smith wrote: > On Tue, 7 Sep 2004, Guillaume Fougnies wrote: > > >Mon, Sep 06, 2004 at 11:56:21PM -0700: Darren Duncan wrote: > >> > >> What you probably saw with the 3ms is the time between when you > >> iss

[sqlite] concurrency in sqlite 3.0

*) is locked or unlocked could be great; Allowing to manage cond signals on the busy stack of many waiting (sqlite*). This could allow to manage fine tuned policies on request priority like some RT systems need. Is this sound crazy? :) Or is there another way to manage this without featuring SQLite? Thanks, bye. -- Guillaume FOUGNIES

[sqlite] multiple indexes.

does not use the t2 index on 'id' to speed up the join. In my case, t2 is quite big. The only "solution" i see could be to split the request in two to use indexes on both tables... Can anyone advise me? Thanks. Bye, -- Guillaume FOUGNIES

Re: [sqlite] Busy handlers in SQLite3

API if > they don't work properly. But maybe I've overseen something. > > Don't get me wrong: I like the new API a lot :-) > > -- Gerhard -- Guillaume FOUGNIES

Re: [sqlite] Library routine called out of sequence

calling? > > Thank you. > P. Morandi -- Guillaume FOUGNIES

Re: [sqlite] SQLITE_OMIT_*

_OMIT_ALTERTABLE" ./configure --enable-threadsafe > --disable-tcl > make clean > make # fails during make -- Guillaume FOUGNIES