Val

Hi. Yes, this is a known problem. Can you mention all the steps to reproduce the problem? I would like to write a test on this as i don't have...

Hi, You can get all the results from cursor by calling `mc_cursor:rest/1`

Thanks, I'll check it.

Just prefer using maps instead of bson tuples. Maps are supported and written in spec: ``` -spec update(pid(), collection(), selector(), map()) -> {boolean(), map()}. ```

Thanks, I'll check it out.

Just rechecked with test. You can either update document with `$set` like in `update` test: ``` Command = #{ => 500, => #{ => "14Q3"}, %with flatten_map there is no...

Thanks, I'll check it out.

maybe it is killed because the connection is closed? Can you please try with `{ok, Connection} = mc_worker_api:connect ([{database, Database}]).`

why should we wait after error was detected?

I think some top supervisor should be responsible for worker restart delay. Not the worker itself, as it know nothing about will it be restarted or not.