Noticed this pattern in Exposed as well and I think this really adds a lot of friction and overhead to using such a solution. Does kdbc offer a work around for this?