mirror of
https://github.com/OpenMW/openmw.git
synced 2025-02-01 19:45:35 +00:00
a75c7c49f0
Simultaneously writing to sqlite3 database is not possible. Process exclusively locks the database for this. Another process will fail to perform any request when database is locked. Alternatively it can wait. Handling this situation properly requires complexity that is not really needed. Users are not expected to run multiple openmw processes simultaneously using the same navmeshdb. Before this change running multiple openmw processes using the same navmeshdb can lead to a crash when first transaction fails to start because there is exception thrown and not catched. Remove use of explicit transactions from DbWorker. Handling all possible transaction states due to different errors brings unnecessary complexity. Initially they were introduced to increase time between flushes to disk. This makes sense for navmeshtool because of massive number of writes but for the engine this is not an issue. |
||
|---|---|---|
| .. | ||
| asyncnavmeshupdater.cpp | ||
| generate.hpp | ||
| gettilespositions.cpp | ||
| navigator.cpp | ||
| navmeshdb.cpp | ||
| navmeshtilescache.cpp | ||
| operators.hpp | ||
| recastmeshbuilder.cpp | ||
| recastmeshobject.cpp | ||
| settings.hpp | ||
| settingsutils.cpp | ||
| tilecachedrecastmeshmanager.cpp | ||