Client: I need to organize this data in my database, just let me create any folder, and folders inside folders. I mean, it is a database so you can create folders right?
Me: I'll see what I can do
Inner me: NO, F U, that's not easy, that's not how databases work, WTH is wrong with you

Well there are some databases that could work almost as a filesystem.

But they are not very common and usually have other drawbacks that make them unsuitable for most database tasks.

Yeah maybe I could have searched for something, but we are already six months into development so...

@Woklos no. Dont go looking for obscure DB because a customer has a misconception of databases.

Odds are the customer really dont understand what they really need.

We see it all the time when customers describe what they want. Once you ask the right question on what they want to achieve you often find a better way to do it that is more traditional.

Standard sql is not the best db for all situations but it is the most versatile.

For extreme performance nosql can be good BUT only if you know exactly what your needs are.

Some searches or operations are way faster and other are all but impossible and also all but impossible to work around and also nosql are not a single type but a conglomerate of technologies like column store, document db, graph database and more. All with their own strengths and weaknesses and different use patterns.

Make sure you understand them before trying to switch ;)

@Voxera We added a varchar column so the client can group the records based on that value, and we simulated a file system splitting the value of the column when we find a /.