Don't try to save which options were used to load the data about juliadb.jl HOT 5 CLOSED

It works better now, but we are still saving the options that were passed. It's mostly harmless, but unnecessary and increases the size of the index. It also adds risk of something going wrong, in case there's something strange in the options we can't deserialize (e.g. a function in a package that's not loaded anymore).

from juliadb.jl.

We don't save the hash of the options in the metadata anymore. We only use it to key _read_cache dictionary - which is more harmless since objects are only needed to have the same hash in a given session and not across sessions.

from juliadb.jl.

We are still saving the options themselves, as part of the chunk objects.

from juliadb.jl.

Well usecache=false should make that get overwritten as well. I'm now a bit unclear what we should be doing instead.

from juliadb.jl.

We removed usecache.

from juliadb.jl.