file.path -> file.paths

[samuelstroschein]

Context

We know that files should be "duplicated"/symliked in a lix in a the future.

unblocks use cases like "this markdown file should be stored in /dev-rel/intro.md for writing and /source-code/website/static/blog/intro.md for ease of publishing"

Proposal

We could define a file.path as a relation to FilePaths. A file id points to a list of file paths. Each file path must be unique. (Don't forget, we can use FOREIGN Keys to ensure consistency LIX-134)

• (+) get the data structure "right" from the get go to enable
• (-) risk of not getting it right :D

Migration is simpler from N -> 1. Than 1 -> N.

The risk of defining a file path as singular seems higher than defining it as multiple. A system that can handle one file under N paths is able to handle a (migrated) system that can handle a file with 1 path.