On Fri, 20 Nov 2009, Dylan Beaudette wrote:
I like this setup as well. However I have noticed one major shortcoming of this approach: when a long-running vector operation is using the SQLite database, no other processes can access vector attributes. I noticed this when performing a large v.patch job. No other vector modules that opened the attribute table would work, or would break with errors. Maybe there is something that can be done to solve this, however, it seems like the single-user nature of SQLite is to blame. One SQLite database per vector seems like a heavy-handed solution, but it would solve some of the problems--- while creating others...
Dylan, Yes, SQLite does not play nicely trying to handle threads for multiple users. Postgres is much better for that. However, from what you write this issue is a concern only infrequently, and those can be done unattended using 'at'. Rich _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
