erangell
commented
2 years ago Maybe the hyperdrive protocol can handle long paths internally in the hypercore structures it uses. If it does, then the only issue would be saving local copies of hyperdrive contents on operating systems that limit path size - in which workarounds would be needed to download files to shorter path directories and maintain the illusion that the shorter path represents the real long path in the hyperdrive.
Long filenames and path names cause issues over a certain length cause issues on certain operating systems. For an experimental system this is OK - don't use it for important data. There is also the issue of logical units of work, where multiple files may need to get updated as a unit in order to avoid data anomalies or inconsistent index structures. Code can be structured so an exception writing any file of a logical unit of work (LUW) invokes compensation actions to rollback changes made to other files in the LUW.
This issue may force the design to use a graph database. It can also be a relational database. However one goal is not to require the user to depend on any specific vendor products. So open source databases can be used if the procedures for maintenance are automated and documented well enough for users to understand.