See http://stackoverflow.com/questions/54998/how-scalable-is-sqlite
[...] there is nothing that prevents using an Sqlite database in a multi-user environment, but every transaction (in effect, every SQL statement that modifies the database) takes a lock on the file, which will prevent other users from accessing the database at all. So if you have lots of modifications done to the database, you're essentially going to hit scaling problems very quick. If, on the other hand, you have lots of read access compared to write access, it might not be so bad. On Apr 2, 12:00 pm, Sven <svenstrin...@gmail.com> wrote: > Hi, > > I programmed a psychological experiment in flash and store answers/ > results in a sqlite database using web2py (behind nginx server + > fastcgi) and pyamf. Everything seems to be all right when I test it, > but with as few as 2 simultaneous users I (sometimes) run into > trouble. A try with seven simultaneous users resulted in only 2 > succesfully stored experimental data.sets > I find it very hard to debug, since there are no tickets in web2py. > Flash does sometimes produce a remoting error in that situation, but > without too much information. > > I seems to me there is some kind of concurrency problem, but I assumed > web2py/sqlite would take care of that for me. Or should I explicitly > deal with this? Explicitly commit, check if inserts and updates were > successful and if not try again? > > Any suggestions, comments ideas would be really appreciated. > > Thanks. > > Sven -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
