Re: [sqlite] Use of sqlite3_step()

On 7/6/10, Andrew Wood wrote: > Whats the procedure for using sqlite3_step? > > I thought it would be along the lines of the following, but the while > loop executes infinately. I would have expected the while loop to run > once for each row found? > > Code is as follows: >

Re: [sqlite] sqlite3_close ==> " library routine called out of sequence"

On 2/24/10, Jean-Denis Muys wrote: > > On 2/24/10 9:36 , "Simon Davies" wrote: > > > Rogue semicolon on line > > > >> if( sqlite3_close( db ) != SQLITE_OK ); > > > > Regards, > > Simon > > > I have been bitten by such silly

Re: [sqlite] performance of select in transactions

On 10/2/09, Pavel Ivanov wrote: > > It seems a bit disingenuous to claim > > there will be no performance gain by putting selects in a transaction, > > when sqlite clearly does less work with the transaction (in the form > > of not getting the read lock multiple times). > >

Re: [sqlite] performance of select in transactions

On 10/2/09, Pavel Ivanov wrote: > > Does anybody know why just adding the begin/commit here improves > > performance? If I have to do a large number of selects like this in my > > application, should I always wrap it in a transaction? > > > This looks like some overhead of

Re: [sqlite] Warning message in amalgamation

On 2/2/09, Roger Binns wrote: > Maurí­cio wrote: > > I know this is not a problem, but I would like to > > remove this warning since it's not important for > > the rest of the code. What could I do? > > > The usual method is to cast the result to (void) but gcc still