Batch write: Doing a delete when the value missing seems prone to mistakes

[Raynos]

Having a batch API that is something like

table.batchWrite([
  { hash: 'foo', range: 'bar', value: { ... } },
  { hash: 'foo': range: 'other', delete: true }
])

Is less likely to delete due to a bug, since the delete is opt in.

we can also add something like

const batch = table.startBatchWrite()
batch.put('foo', 'bar', { ... })
batch.delete('foo', 'other')
const { err } = await batch.commit()

In the future, to support an API with fewer allocations. ( Would be nice to have benchmarks first before doing this ).

[heapwolf]

maybe, im on the fence with this. is having the radix parameter the second positional argument to parseInt a footgun? maybe. maybe not. haha. Let me think about this one more.

[Raynos]

well at least tuple.length instead of if (value) because the current implementation would do a delete instead of writing null for batchWrite(foo, bar, null)

Also that's another issue I should open about objects vs primitive.