Bug #1010

Engine db_mode 1 isn't accessible from mod and LuaSQL

Added by Spyhawk over 2 years ago. Updated over 1 year ago.

Status:New% Done:

0%

Priority:NormalSpent time:-
Assignee:-
Category:General
Target version:2.78
OS: Arch:

Description

The in-memory db mode (db_mode 1) create the engine database in memory, but while the mod and LuaSQL can access it, the table created in engine aren’t visible to them.
On-disk memory mode (db_mode 2) is actually used as default as a fallback.


Related issues

Related to ET: Legacy Development - Feature #403: Add bayesian skill rating Fixed 23.12.2018
Related to ET: Legacy Development - Task #975: Add WolfAdmin to installers Feedback 15.01.2017

Associated revisions

Revision d8642636
Added by IR4T4 over 2 years ago

Dynamite planted!

Revision 93c2dfbd
Added by Spyhawk over 2 years ago

db: use db_mode 2 by default for now

Dynamite defused! See d8642636209bb347b0608aedeb5d0b8a83d53ef2

Revision 0e7fd9fb
Added by Spyhawk over 2 years ago

general: use SQLite shared cache with db_mode 1

Revision 1bfae65b
Added by Spyhawk over 2 years ago

luasql: readded SQLITE_OPEN_SHAREDCACHE, refs #1010

Revision 00486137
Added by IR4T4 over 2 years ago

db: added check for enabled shared memory db

History

#1 Updated by Spyhawk over 2 years ago

#2 Updated by IR4T4 over 2 years ago

  • Related to Task #975: Add WolfAdmin to installers added

#3 Updated by IR4T4 over 1 year ago

  • Priority changed from High to Normal

#4 Updated by Spyhawk over 1 year ago

  • Target version changed from 2.76 to 2.78

Also available in: Atom PDF