What If OpenDocument Used SQLite?

Re:What If OpenDocument Used SQLite? by rakoo on Monday September 18, 2023 @09:16AM (#37555683)

You are right, this is a use case I absolutely did not take into account, but I want to separate user-defined actions and app-defined actions. A level of zoom is something a user does to read a document, but I wouldn't consider that as data to be persisted automatically, unlike characters typed or a font chosen. I value the idea of persisting it, but that would be a user-specific action ("Save view" or something like that)

In the case of checksums in a database, that is why read-only modes should be used and I don't see what automatically saving would change. If anything, when the user zooms on a document in read-only mode, either it shouldn't be stored or storing it should trigger the same flow as modifying the document

[ Parent | on HN ]

Re:What If OpenDocument Used SQLite? by fluidcruft on Monday September 18, 2023 @11:26AM (#37557508)

I see what your are saying, but in other use cases the presentation state needs to be considered as part of the document. This is one of the reasons zip/jar containers work somewhat well. You can audit different chunks of data separately and cryptographically sign them. sqlite actually has an archive format[1] that is interesting to think about and I have pondered using it for some applications (store the files and also store tables of metadata/analysis)

[1] https://sqlite.org/sqlar.html

[ Parent | on HN ]

Re:What If OpenDocument Used SQLite? by atoav on Monday September 18, 2023 @02:09PM (#37559731)

Why not do it like Blender: just autosave into some software directory, have the possibility to restore on crash, have the possibility to restore the last n autosaves from disk and add a setting for how many to save etc in the options.

[ Parent | on HN ]