This adds a new LMDBStorage class, which uses LMDB for storing game data. This is a no-SQL database, and thus likely more efficient / suitable for the needs than the SQLite-based storage. With this, we can close #2.
This required a lot of additional refactorings, some of which were already merged to master directly and others are included in this PR. Notably, storage can now throw a RetryWithNewTransaction exception, which will be handled by the Game instance and it will reinitialise and retry the update. This is used to resize the LMDB map as needed.
This adds a new
LMDBStorageclass, which uses LMDB for storing game data. This is a no-SQL database, and thus likely more efficient / suitable for the needs than the SQLite-based storage. With this, we can close #2.This required a lot of additional refactorings, some of which were already merged to
masterdirectly and others are included in this PR. Notably, storage can now throw aRetryWithNewTransactionexception, which will be handled by theGameinstance and it will reinitialise and retry the update. This is used to resize the LMDB map as needed.