[sqlite] NOP INSERT still writes to the DB/journal

Hello, On Mon, Dec 7, 2015 at 5:05 PM, Patrick Donnelly wrote: > Update on this: > > On Mon, May 5, 2014 at 4:53 PM, Patrick Donnelly > wrote: >> Hi, >> >> I have an INSERT that looks like >> >> INSERT INTO T >> SELECT ... >> >> which I'm running numerous times a second that generally

[sqlite] NOP INSERT still writes to the DB/journal

On 2015/12/08 12:16 PM, Domingo Alvarez Duarte wrote: > If I understood correctly when no transaction is specified an implicit > transaction is created so there is no point to create a transaction for only > one statement. Yes, but what Simon is trying to achieve is to have the transaction

[sqlite] NOP INSERT still writes to the DB/journal

On 8 Dec 2015, at 10:16am, Domingo Alvarez Duarte wrote: > If I understood correctly when no transaction is specified an implicit > transaction is created so there is no point to create a transaction for only > one statement. The OP here has lots of INSERT commands and is complaining that

[sqlite] NOP INSERT still writes to the DB/journal

If I understood correctly when no transaction is specified an implicit transaction is created so there is no point to create a transaction for only one statement. Cheers ! > Tue Dec 08 2015 5:51:35 am CET CET from "Simon Slavin" > Subject: Re: [sqlite] NOP INSERT still w

[sqlite] NOP INSERT still writes to the DB/journal

On Mon, Dec 7, 2015 at 11:51 PM, Simon Slavin wrote: > > On 8 Dec 2015, at 12:19am, Patrick Donnelly wrote: > >> There are still writes: > > Because you have not defined any transactions, each of your INSERT commands > it getting wrapped in its own transaction. A transaction has to involve >

[sqlite] NOP INSERT still writes to the DB/journal

lists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Domingo Alvarez Duarte > Sent: Tuesday, 8 December, 2015 03:17 > To: SQLite mailing list > Subject: Re: [sqlite] NOP INSERT still writes to the DB/journal > > If I understood correctly when no tr

[sqlite] NOP INSERT still writes to the DB/journal

On 8 Dec 2015, at 12:19am, Patrick Donnelly wrote: > There are still writes: Because you have not defined any transactions, each of your INSERT commands it getting wrapped in its own transaction. A transaction has to involve writes to disk. Try this ... BEGIN INSERT INTO t1 ... END See

[sqlite] NOP INSERT still writes to the DB/journal

On Mon, Dec 7, 2015 at 5:31 PM, Igor Tandetnik wrote: > On 12/7/2015 5:05 PM, Patrick Donnelly wrote: >> >> No rows were inserted but there are several writes. This behavior >> seems to be caused by AUTOINCREMENT? > > > Could be creating sqlite_sequence table where there wasn't one before. I >

[sqlite] NOP INSERT still writes to the DB/journal

On 12/7/2015 5:05 PM, Patrick Donnelly wrote: > No rows were inserted but there are several writes. This behavior > seems to be caused by AUTOINCREMENT? Could be creating sqlite_sequence table where there wasn't one before. I wonder if there are still writes on the second and subsequent no-op

[sqlite] NOP INSERT still writes to the DB/journal

Update on this: On Mon, May 5, 2014 at 4:53 PM, Patrick Donnelly wrote: > Hi, > > I have an INSERT that looks like > > INSERT INTO T > SELECT ... > > which I'm running numerous times a second that generally does nothing > because the SELECT returns no rows. Unfortunately, I've found that >

Re: [sqlite] NOP INSERT still writes to the DB/journal

On Mon, May 05, 2014 at 05:00:08PM -0400, Richard Hipp wrote: > On Mon, May 5, 2014 at 4:53 PM, Patrick Donnelly wrote: > > > Hi, > > > > I have an INSERT that looks like > > > > INSERT INTO T > > SELECT ... > > > > which I'm running numerous times a second that

Re: [sqlite] NOP INSERT still writes to the DB/journal

On Mon, May 5, 2014 at 4:53 PM, Patrick Donnelly wrote: > Hi, > > I have an INSERT that looks like > > INSERT INTO T > SELECT ... > > which I'm running numerous times a second that generally does nothing > because the SELECT returns no rows. Unfortunately, I've found

[sqlite] NOP INSERT still writes to the DB/journal

Hi, I have an INSERT that looks like INSERT INTO T SELECT ... which I'm running numerous times a second that generally does nothing because the SELECT returns no rows. Unfortunately, I've found that SQLite still does numerous disk writes anyway in this situation. Is my only option to