[Bug]: moving datahike-db folder to another location does not allow the db to start

[awb99]

What version of Datahike are you using?

0.6.1594

What version of Java are you using?

openjdk 21

What operating system are you using?

linux nix

What database EDN configuration are you using?

(def cfg {:store {:backend :file
:path (str data-path "datahike-db")}
:keep-history? false
:schema-flexibility :write ;default - strict value types need to be defined in advance.
})

Describe the bug

I recently have moved the location of where the datahike db is located on my server.
So I have changed :path in the setting.
And that lead to the db connection not being able to start.
To be fair, there was a message, that I could put in another setting to let it work, but this
is a very weird behavior. Why does the database care from which path it is being loaded?
I dont think there should be a setting for this. Our database is backuped to some storage,
and might be loaded to a new machine with a slightly different folder location. Why is this
a problem?

What is the expected behaviour?

Load DB from a folder specified.

How can the behaviour be reproduced?

create a db, which will create the folder.
then move the folder to a different location
then change the config to use the different folder.
the new connection will not work.

[whilo]

The configuration uniquely identifies a database in a memory system and the configuration check is there to make sure you are connecting to the intended database and not another one, potentially corrupting it with an incompatible configuration. It is maybe a bit too defensive, we could ignore the :store config settings completely for the check. I mostly put it there to make sure people do not corrupt their databases.