The reader processes create all the papared statements at startup, so they would be parsed only once.
then, whenever they need to read from the db, they just reset, bind and step the prepared statements i already had. Is that wrong? On Mon, Nov 28, 2011 at 3:15 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 28 Nov 2011, at 5:10pm, Alejandro Martínez wrote: > >> I have one process that writes on a database. It "realoads" tables by >> filling a new table and then replacing the old one via a drop and a >> rename within a transaction. >> >> Then there are several processes that just read from this database. >> >> I don't want these "readers" to block, so i made the database "wal". >> >> The thing is, it seems this "readers" don't ever see any changes in >> the db unless i shut them down and run them again. > > What functions are you using to read ? Are you preparing one statement when > the read processes begin, and just using this the whole time ? Or are you > doing many separate "SELECT" statements ? Or something in between ? > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
