Fastonosql didn't warned me that I was overwriting a file on my database #83
Description
I was trying to open a LevelDB of 556 GB on Fastonosql but it frozen when clicking on the folder.
Then it was killed by the operational system.
So I tried entering the path directly, then Fastonosql recognized it (passed on test) and opened it, but it didn't loaded any data.
So I tried entering the path again, but this time I left a ldb file from the database on the path, it failed on the test but anyway I tried to open it. Then it frozen again so I killed it.
After that the database appears to be corrupted, complaining of a missing file, specifically the one that that I tried to open.
This was clearly a user mistake, however it's a bad UX to Fastonosql. I suggest implementing sanity checks before writing a file to a path.