default_create_parameters in configuration are also used for reading

[andreasbaumann]

The parameter for storage creation and storage usage should be strictly
separated. Also not quite sure what happens if storages are opened with
different parameters than they were created (e.g. compression, block_size).

[andreasbaumann]

The main reason for the mixture is that the storage options are available for create as well as for open in leveldb. I think leveldb ignores global storage behavior options when opening a storage without option create_if_missing set. The create_if_missing option is also available in the strus createStorageClient interface as configuration option 'create=yes'.

I agree that this problem should be solved, but I do have an idea how to solve it.

[andreasbaumann]

I think I just split the configuration options in a 'create' and in a 'default' section to
make things clear in the webservice.

[patrickfrey]

That's an argument in general, but not urgent now as leveldb is the only implementation. We should consider this idea in the future.