I think @RelationId decorator is great to solve this issue. You can still save using { statement: 1 }, not { statementId: 1 }, while your objects are always going to have statementId. It also doesn't create a spare column in the DB.

Wow! Thank you @matviienkont! I just looked at this decorator briefly, but it does look like it solves the issues that I mentioned and it's easy to add even to existing entities!! Thank you! I'm going to experiment a bit more, and then I'll write up another document explaining to developers what we should do from now going forward.