Skip to content
This repository was archived by the owner on Apr 4, 2024. It is now read-only.
This repository was archived by the owner on Apr 4, 2024. It is now read-only.

more robust database handline #349

Description

@rebeccamadsen

When a database file fails to load for any reason, Server gives an error message and then exits. It would be better to handle corruption of the individual database files separately, and not have the whole app fail to launch when possible to continue. We should also explore ways to make processing the databases more robust if possible.

For example, when a database gets corrupted, "NUL" characters show up in the .db file and prevent processing. This is perhaps occurring when the app closed unexpectedly or too soon, or that there is a rare scenario where our write code is broken. Example issues that deal with the null data are here louischatriot/nedb#480 and here louischatriot/nedb#646.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions