that seemed a bit more invasive. i would rather do this once we look at child strategy support explicitly. until then i much rather just call into this here without mixing the translation strategy code with the query builder code.