On 22 Dec 2010, at 13:12, Simon Slavin wrote: > > You do mention something worthwhile: if you had a server/client version of > SQLite you could get rid of all the code to do with file sharing and locking. > That's quite a lot of code, if you include all the PRAGMAs and related > programming that could be ignored. > > You will need some way to keep multiple connections straight -- each one has > its own transaction and rollback status. But you have the advantage that one > process knows everything that needs to be known: it can all be handled by one > process, that process knows everything it has to know, and it can keep > everything it needs in memory.
You would need to reintroduce practically everything you think you can get rid of if you wish to ensure that there is only one process and you are intending to provide a facility for two transactions to be active concurrently. Phil Willoughby -- Managing Director, StrawberryCat Limited StrawberryCat Limited is registered in England and Wales with Company No. 7234809. The registered office address of StrawberryCat Limited is: 107 Morgan Le Fay Drive Eastleigh SO53 4JH _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
