Enable in memory (no file access) mode. Can be useful for unit tests. File path will be used as db identity (default: false).
Doing some experimentation we found that using integer keys we can get the database to work faster and save some space. Additionally, for in-process databases there are almost no drawbacks versus globally unique keys. However, at the same time, it is relatively hard to keep unique integer keys outside of the database engine, so we made it part of the database engine code. Generated keys will be unique in the collection scope (default: false).
Maximum number of cached objects per collection (default: 1000).
Maximum size of objects that can be placed in the cache (default: 1024).
Globally enables support of search in nested arrays. MongoDB supports this unconditionally. For TingoDB, searching arrays when there are no arrays incurs a performance penalty. That's why this is switched off by default. Additionally, and this might be a better approach, nested array support can be enabled for individual indexes or search queries.
Maximum size of objects that can be placed in the cache (default: 1024).
Maximum number of cached objects per collection (default: 1000).
Enable in memory (no file access) mode.
Enable in memory (no file access) mode. Can be useful for unit tests. File path will be used as db identity (default: false).
Doing some experimentation we found that using integer keys we can get the database to work faster and save some space.
Doing some experimentation we found that using integer keys we can get the database to work faster and save some space. Additionally, for in-process databases there are almost no drawbacks versus globally unique keys. However, at the same time, it is relatively hard to keep unique integer keys outside of the database engine, so we made it part of the database engine code. Generated keys will be unique in the collection scope (default: false).
Globally enables support of search in nested arrays.
Globally enables support of search in nested arrays. MongoDB supports this unconditionally. For TingoDB, searching arrays when there are no arrays incurs a performance penalty. That's why this is switched off by default. Additionally, and this might be a better approach, nested array support can be enabled for individual indexes or search queries.
TingoDB Options