Sqlite3 DB => Regular Directory => Same+ Sqlite3DB Roundtrip

Forums Personal Topics Unbidden Thoughts Sqlite3 DB => Regular Directory => Same+ Sqlite3DB Roundtrip

This topic contains 6 replies, has 1 voice, and was last updated by  josh March 13, 2021 at 1:52 pm.

  • Author
    Posts
  • #86408

    josh

    Strategies for checking coherence of the rebuild? I suggest a conceptual classification of 3 tiers:

    I – things that have no supported evolution outside of the Sqlite program
    II – things which can be edited but require extra compute checking on rebuild
    III – things which are treated as data and are inexpensive to edit

    In the filesystem,

    items in set I are stored in the filesystem as read-only & secure hash is stored to check their integrity on rebuild.

    items in set II are securely hashed in more elaborate ways to identify exactly what changed & what did not

    items in set III are in rw files for the user.

    Creation options affect what is stored in each set & maybe how it is stored. Creation os items in set II implies longer processing.

    • #86409

      josh

      Another concept – start with visudo, but turn it into a script that creates an in-memory (or other temp) text buffer & then does something with it on close. The script can then provide extra levels of conformance checking for the modification to the file archive, which happens on close/save.

  • #86411

    josh
  • #86413

    josh
  • #86415

    josh
  • #86417

    josh

You must be logged in to reply to this topic.