Ability to disable `ensure-stored-config-consistency` about datahike

[alekcz]

Lemme work on making store-identity more robust.

[alekcz]

@whilo @TimoKramer thoughts?

[whilo]

I think disabling might not be the best idea. The problem is once you connect to a store with a potentially incompatible configuration you might corrupt the database. I agree that the jdbcUrl should be allowed to be different for the hostname and port. Maybe we could provide a multimethod that is implemented by every store and only returns the part of the config that should be matched.

[whilo]

store-identity is supposed to do that, I need to check again how it works for JDBC. Alternatively we could still use the random names and add them to every store and just rely on that.

[alekcz]

@whilo I've almost completed the store-identity work on datahike-jdbc. The missing part in on the datahike side. The comparison doesn't use the store-identity: https://github.com/replikativ/datahike/blob/166cdbbb7031fa03e619091fb7a99c20cd550ec3/src/datahike/connector.cljc#L126C18-L126C18

[whilo]

Right, I think it should break out the store config there and run store-identity on it and then equality check that.

[alekcz]

Resolved by #655