Test passed!


Thursday, February 25, 2010 at 6:01 pm

If you have been following these posts then you will be aware that a problem was encountered with data corruption when a number of concurrent usesr were hitting the same data files. This problem has now been solved.  There’s some tidying up of the code to be carried out – it was important to get [...]

Building and Rebuilding


Sunday, February 21, 2010 at 10:21 am

First, the rebuilding.  The Railroad and Parameters modules have been rebuilt, and work continues on the User module.  After that, there are a further three modules to be rebuilt before a further volume test takes place; but irrespective of the results of that test (providing the test is not an absolute failure) work will continue [...]

SQLite


Wednesday, February 17, 2010 at 5:12 pm

Some time has been spent today becoming familiar with how SQLite fits in with Python; and it has been reasonably painless!  A couple of transactions have already been built for MOPS, and the aim now is to convert a substantial amount of MOPS to use the SQLite database and then to give it the same [...]

Tricky…


Tuesday, February 16, 2010 at 2:35 pm

Further to the post earlier today, it appears that there may be a while to wait for MySQL to be available to Python users: Python v3 is not that long out of the box (and that is what MOPS has been written in) and the MySQL adaptors are still awaited.  So, it’s a choice between [...]

One step forward, one step back


Tuesday, February 16, 2010 at 11:01 am

Although it’s not expected that MOPS will be a heavy user of data, it still needs to support a small number of concurrent users without any significant issues.  Initially, MOPS was built with a file-locking mechanism; but testing with multiple concurrent users accessing the same data started showing some file corruption. Changes to the file-locking [...]