I don't think that the TMP folder is the right direction but I'll check it anyway with the hosting company. besides that, I do know that there is only one process running that tries to write to the database what makes my situation a sad joke. sqlite supposed to be a strong database that knows how to deal such simple situations. even of 2 processes that tries to write to the database the same time, else it's probably a very weak database system that doesn't have transactions locks mechanism inside.
does anyone knows if sqlite got any connection string definitions that deals with locks? or any other setting that influence the enviroment? Shahar. 2012/1/29 Simon Slavin <slav...@bigfraud.org> > > On 28 Jan 2012, at 11:47pm, Jan Hudec wrote: > > > On Sun, Jan 29, 2012 at 00:43:07 +0200, Shahar Weinstein wrote: > >> I know there is no permissions problems since after some time when I try > >> the same action, it succeeds. in the website, I manage to > read/write/delete > >> in different locations of the code. > > > > Can it be that the database is really locked by another request running > in > > parallel? Sqlite only allows one writer to the whole file and unless you > set > > WAL mode, no readers while writing. > > If I get the setup correctly, this is a web-facing app. Some web servers > start a process for each HTTP session, or for each item they serve. That > means that even though he has only one application that accesses the > database (an active web page) he might have two concurrent processes using > the SQLite API to access the database. > > 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
