Re: [sqlite] Reading across processes on Solaris

2007-04-01 Thread Charles Cazabon
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 develo

Re: [sqlite] Reading across processes on Solaris

2007-04-01 Thread Joe Wilson
> 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 applicatio

Re: [sqlite] Reading across processes on Solaris

2007-04-01 Thread Charles Cazabon
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 whatever

Re: [sqlite] Reading across processes on Solaris

2007-04-01 Thread Joe Wilson
--- 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 da

Re: [sqlite] Reading across processes on Solaris

2007-04-01 Thread Joe Wilson
--- 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 da

[sqlite] Reading across processes on Solaris

2007-04-01 Thread Charles Cazabon
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 sta