This is only necessary because we define multiple record classes with the same table name but incompatible key definitions. That is not something that should ever happen in a realy usage. It is a strange artifact in our tests, though, and my least favorite part of this PR. Perhaps we could (over time) refactor out tests to use more meaningful record class names and there by remove the need for the mechanical uniqification?