dragotin
commented
1 year ago Hm, not sure yet what you intend to do, but: Please check the branch newshared.
It contains an implementation where documents are not longer stored in the database, but completely in the file system as XML files. I should certainly write more about it, but it is moving forward as you see on the commits going into it. I plan to release it as version 2.0 as soon as it is useable.
The goal of that is in a very few words:
- have documents and other data (eg. numbercycles) as xml files that can be synced with ownCloud and shared between Kraft instances running distributed.
- reduce the usage of the database dramatically and only for data that concerns the local instance. (That will take time..)
- only support Sqlite for that
In the new design, UUIDs will be a vital part of the story as you can see in the the example XML file.
Maybe this solves your issues already? As that will be the "new Kraft" moving forward, please verify all ideas against that and let me know what you think.
In preparation for the following feature request it will be necessary to modify database requirements or add code to check the database version.
I would recommend mariadb >= 10.6 as minimum requirement but could settle for mariadb >= 10.5 and MySQL >= 8.0
Reason: GUID generation and handling. Currently only PostgreSQL and mariadb 10.6++ permit using them with minimal pain.
MySQL is not generating GUID v4 but v1 and needs manual compression into binary form, mariadb 10.5 is not much better.