[sqlite] SQLite with wall enabled what's wrong C demo

> Le 24 mars 2016 ? 14:46, Domingo Alvarez Duarte dev.dadbiz.es> a ?crit : > > But in this example there is only one application accessing the database and > only one table with one small record been updated all the time and no active > readers, why it's writing to wal ? Because it is engineered

[sqlite] SQLite with wall enabled what's wrong C demo

d why not update the same record instead of adding a new one in such situation ? I'll try with a bigger record to see what happens. Cheers ! ? > Thu Mar 24 2016 11:55:11 AM CET from "Domingo Alvarez Duarte" > Subject: [sqlite] SQLite with wall enabled >w

[sqlite] SQLite with wall enabled what's wrong C demo

Thanks for reply ! The error check was left out intentionally to not pollute the code, I stepped through all code with gdb to certify it's doing all correctly. Cheers ! > Thu Mar 24 2016 12:03:28 PM CET from "Stephan Beal" > Subject: Re: [sqlite] SQLite with wall en

[sqlite] SQLite with wall enabled what's wrong C demo

On Thu, Mar 24, 2016 at 11:55 AM, Domingo Alvarez Duarte < sqlite-mail at dev.dadbiz.es> wrote: > There is something wrong with the program or with sqlite3 ? > > > rc = sqlite3_bind_text(stmt_insert, 1, session_id, > sizeof(session_id)-1, NULL); > rc = sqlite3_bind_text(stmt_inse

[sqlite] SQLite with wall enabled what's wrong C demo

Hello ! I'm sending here a C program that demonstrates the problem of sqlite3 in wall mode, in this simple example of a simulated session management for a web server when executing the wall log file will grow and grow till eat all our disk. ? There is something wrong with the program