ordered insertMany on tables does not insert anything if there's a bad row in the middle

[hemidactylus]

Symptom: insertMany on tables, when ordered=True and there's a faulty row in mid-list, does not insert even those coming prior to that one.

This is at odds with Collections (ordered=true), where the docs are inserted sequentially until the erroring one.

Also in that case the response has no "status" field at all.

(first reported here).

[hemidactylus]

It was later clarified that if by "faulty row" one means "a row with a wrong type", then the fact that no insertions occur is by design: Tables do preemptive all-rows data validation and this is the expected behaviour.

[amorton]

re-open as we are discussing