Hello! I’ve been wondering for a little about the reasoning behind the 10 MB limit on inserting files into a CherryTree database. It would be nice to be able to store files larger than this limit, if it were possible. Is this a limitation behind CherryTree’s file format, or something else?
Some years ago we found during testing, that with attachments in the size of some MB CherryTree became terribly slow, partially behind usability. I do not remember the details of the discussion at that times, but I remember, that I found and reported the problem during beta tests.
Oh, I see! Interesting…well, it’s true that some nodes with lots of embedded files in them do tend to take a little while to open. But in general it’s better to separate them out in different nodes when possible, mitigating this quite easily. Are there any risks involved with increasing that limit, via the embfile_max_size setting, out of curiosity, or is it merely a matter of usability and response times?
I cannot answer the question regarding risks from own experience, because I do not see the sense of doing this. In general: if you do regularly a backup of your CT file, than you will be able to revert to the previous version in case needed.
Besides that: I wonder where the sense is in attaching such byte monsters. CT is not meant to be a file container like e. g. a ZIP file. Attaching huge files gives in any case the disadvantage, that every backup will take much more time and more disk space, as those attachments will get backed up every time, even if the attachment itself has not been altered in any way. Putting a link to a file appears to me as the more appropriate method