Would it make sense to use a graph DB to model file hierarchies (folders and subfolders) at scale? (hundreds of thousands of folders) The idea would be to use

Would it make sense to use a graph DB to model file hierarchies (folders and subfolders) at scale? (hundreds of thousands of folders) The idea would be to use a graph DB for a first query to get the file ids in scope (all files inside a given folder and its subfolders) before running the actual SQL query, eg creation_date < foo AND file_id in [array from graph db output]