Re: [sqlite] Reading across processes on Solaris

Joe Wilson <[EMAIL PROTECTED]> wrote: > > I'll continue investigating and try to get to the bottom of this. Thanks > > for the sanity-check. > > Might there be some autocommit/sql statement batching difference for the > driver or your app on different platforms? No; one of the beauties of

Re: [sqlite] Index creation

I did two things: 1. Catted the file to /dev/null 2. Reduced cache_size from 1 down to 2000 I don't know what actions enabled the creation of the index. Before I did these two things, the index would not create. Joe Wilson wrote: > > --- Joe Wilson <[EMAIL PROTECTED]> wrote: >> >

Re: [sqlite] Reading across processes on Solaris

> I'd have thought so, too. I've confirmed fdatasync shows up in the symbols in > the compiled sqlite library, and that two instances of the `sqlite3` SQL shell > don't show the problem. Unfortunately, two minimal Python programs don't show > the problem either. > > That points to the

Re: [sqlite] Reading across processes on Solaris

Joe Wilson <[EMAIL PROTECTED]> wrote: > --- Charles Cazabon <[EMAIL PROTECTED]> wrote: > > > > On most platforms, the reader sees new data appear in the database > > periodically as the writer creates new records. But on Solaris, the > > reader never sees any updates -- it only ever sees

[sqlite] testing with single source file

[EMAIL PROTECTED] wrote: [...] In past releases of SQLite, we have made available a ZIP archive with preprocessed source files. In the future, we may change this so that instead of a ZIP archive full of individual files, we ship a single "sqlite3.c" source file which contains all of the source

Re: [sqlite] Reading across processes on Solaris

--- Charles Cazabon <[EMAIL PROTECTED]> wrote: > I'm using sqlite (through the pysqlite wrapper, but this behaviour seems > unrelated to the wrapper) in an application on various platforms. One process > create an sqlite database and starts writing data to it; another process opens > the sqlite

Re: [sqlite] Reading across processes on Solaris

--- Charles Cazabon <[EMAIL PROTECTED]> wrote: > I'm using sqlite (through the pysqlite wrapper, but this behaviour seems > unrelated to the wrapper) in an application on various platforms. One process > create an sqlite database and starts writing data to it; another process opens > the sqlite

[sqlite] Reading across processes on Solaris

Greetings, I searched the web and the list archives but found nothing relevant to this problem, so here goes... I'm using sqlite (through the pysqlite wrapper, but this behaviour seems unrelated to the wrapper) in an application on various platforms. One process create an sqlite database and