Thanks. I have found that the select statement was issued inside a transaction. Could this cause sqlite to make changes to the database? I also observed that if I mark the database as readonly and issue a select statement inside a transaction (what the application was doing) I get "attempt to write a readonly database" error so it looks like sqlite is trying to have write access to the database even thought it is not needed.
Could this have caused database corruption? Simon Slavin-3 wrote: > > On 9 Apr 2011, at 02:47 PM, giorgi giorgi <mcnamara...@gmail.com> wrote: > >> The application is only issuing select statements (no >> insert/update/delete >> or vacuum) so I cannot understand what could have caused database >> corruption. > > Almost definitely a problem with your hardware, or possibly an > operating-system glitch. I'm not going to pretend that SQLite is bug-free > but if you're not executing write commands it has no reason to write > anything at all. > > Simon > -- > Sent while away from my computer. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://old.nabble.com/Sqlite-database-corrupted-tp31359173p31364155.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
