I'm working on a Rails application that is multi-threaded. A user can start a tool from a web-form that may take several minutes to finish and that writes status-updates in the database (the tool is started in a separate thread). The user can check the current status on a status-page that refreshes itself regularly and reads the current state from the database.
Now, this works fine so far, but i am not able to test my scenario - i guess due to the limitations of sqlite to handle concurrency. The information written in the database by the tool-execution-request is invisible for the tool-execution-thread. Any idea how to solve that issue? Is there a kind of flush() for sqlite to force that the data is made available for the other thread?