2. Likewise for 'read-only?' and 'create?'.
I am not sure about this one. read-only? is not necessarily supported by all databases. Making it mandatory will force the implementation to emulate it. So far, FDB doesn't support read-only?
Read-only is trivial to support in the exported procedures: just keep track of it and have all mutation operations check it before doing anything else.
create? is also subject to this. FDB doesn't have such a concept.
So FoundationDB does not let you create a database using the API?
It seems to me, it is very unlikely that someone will scan the whole database for production purpose. The only usecase I can think of is for debugging, in that case
there is
okvs-debug. I think specifying the maximum key is not a good idea. Let me know what you think.
I'm thinking of use cases like the index is a timestamp and you have read up to a certain point and want everything else. But of course you can use the current timestamp as a terminus in that case. I'm just thinking of a sequential file style of use, where you want to read to the end of file, whatever that may be.