Re: [sqlite] Update/Delete problem

Hi, I have tried closing and opening the applications, but the problem is still there. I have tried to commit the changes for SQLLite Database Browser, but SQLLite is responding with the message "No active transactions". I'm sure that it is the same database, because I rename it and tried

Re: [sqlite] parallelizing an update

I would be very interested to see some benchmark, just to see. On Mon, Feb 1, 2010 at 5:16 PM, Nicolas Williams wrote: > On Sat, Jan 30, 2010 at 10:36:56AM +0100, Sylvain Pointeau wrote: > > echo "begin transaction" >> update.sql > > > > sqlite3 -separator $'\t'

Re: [sqlite] Update/Delete problem

I never said that it has something to do with transaction isolation - if you have no transactions active then there's nothing to isolate. Again: if after restart of applications they still see their own changes and don't see other's changes then you definitely working with different databases.

[sqlite] journal files

hey, I am coding for an application wherein i need to check the journal files as in i dont want it to get deleted after the commit. how to go about it? where in the Sqlite3.c code can i edit it. also, is it possible to customize the sqlite code for the journal file a bit as per my needs? thanx

Re: [sqlite] journal files

What do you want to see in journal files? You can execute 'PRAGMA journal_mode = persist' and all information in journal file except first 4 bytes will be left on disk for you. Is it enough? Pavel On Tue, Feb 2, 2010 at 7:00 AM, rishabh wrote: > > hey, > > I am coding

Re: [sqlite] journal files

Actually, I believe the entire 28 byte header is zeroed, not just the first 4 bytes. See the zeroJournalHdr() function in pager.c for details. -Shane On Tue, Feb 2, 2010 at 7:09 AM, Pavel Ivanov wrote: > What do you want to see in journal files? You can execute 'PRAGMA >

Re: [sqlite] parallelizing an update

On Tue, Feb 02, 2010 at 09:23:36AM +0100, Sylvain Pointeau wrote: > On Mon, Feb 1, 2010 at 5:16 PM, Nicolas Williams > wrote: > > Now to parallelize this: > > > > function par_updates { > I would be very interested to see some benchmark, just to see. Feel free to

Re: [sqlite] Update/Delete problem

On Tue, 2 Feb 2010 09:20:29 +0100, Carsten Peyk wrote: >Hi, > > I have tried closing and opening the applications, > but the problem is still there. I have tried to > commit the changes for SQLLite Database Browser, > but SQLLite is responding with the message "No > active

Re: [sqlite] parallelizing an update

Robert Citek wrote: > Are there some white papers or examples of how to do updates in > parallel using sqlite? > > I have a large dataset in sqlite that I need to process outside of > sqlite and then update the sqlite database. The process looks > something like this: > > sqlite3 -separator $'\t'

Re: [sqlite] parallelizing an update

On Tue, Feb 2, 2010 at 3:13 PM, John Elrick wrote: > Robert Citek wrote: >> Are there some white papers or examples of how to do updates in >> parallel using sqlite? > > I could be misunderstanding your requirements, but this sounds a little > like Map Reduce: > >

Re: [sqlite] parallelizing an update

Please just don't forget that sqlite lock the file at each update, running multiple processes will not improve at all the speed, I think it will be even worst. The only improvement you can do is to group your update in a single transaction, and avoid to run one process (sqlite3) for just 1 update.

Re: [sqlite] parallelizing an update

arg sorry I miss your LRP (Long Running Process), On Tue, Feb 2, 2010 at 11:55 PM, Sylvain Pointeau < sylvain.point...@gmail.com> wrote: > Please just don't forget that sqlite lock the file at each update, > running multiple processes will not improve at all the speed, I think it > will be even

[sqlite] llvm/ppc compile bug

Just a note to share a problem I ran into recently: Compiling sqlite 3.6.22 with -arch ppc -Os on the llvm that ships with Xcode 3.2.1, the sqlite3AtoF function appears to have an infinite loop. If you compile the sqlite3 command line tool in this way, just executing "select round(1234);" will