1. Oh. I screwed up. Thanks for the correction. Apparently, I'm the one that needs to read the info page again! :P 2. This is an interesting case. It's like th

1. Oh. I screwed up. Thanks for the correction. Apparently, I'm the one that needs to read the info page again! :P 2. This is an interesting case. It's like the opposite of .DELETE_ON_ERROR. Anyway, it seems like you have some legitimate workloads that make just doesn't fit well with. Mind sharing the solution you designed?