Table::set should reuse Table::get to fill the cache #6
Assignees
Comments
AlexanderMihail
pushed a commit
that referenced
this issue
Apr 13, 2024
… table as well as any other user-table. The root of the web server is a generated HTML page with navigation for all the system features. There is now a map of tables. Selecting the current table is with the /tablename/?use rest command. Tables can also be dropped. Table::compact was reworked to shift-up deleted keys in the index. An index_revolver coroutine was introduced to return one index per invocation. This logic also has index cleanup capabilities. The Table::list() command uses this coroutine to produce the list of all keys. Table::get/set are now boolean. The set prevents overinserting and updating of unknown keys. The get returns false if the key is unknown. This allows now for inserting or updating "null" values. Better statistics. Better formatted output. All REST logic is in one DefaultHandle where the table list lock is maneaged. Everything the DB server does is listed in the / page which is built by DefaultHandle::build_help. Added the new Table::self_test method and the corresponding /?selftest=0 REST command. This system of self-testing obsoletes the rest.bat file while also aiming at raw performance. This version has problems with deleting keys that are in cache. TODO. This version closes issues: #1, #2, #3, #4, #5, #6, #8. It advances on issues #13 and #11.
|
Done. Relates to #5. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Table::set currently duplicates the logic of Table::get for filling-in the cache for existing keys. This should change.
The text was updated successfully, but these errors were encountered: