Is your feature request related to a problem? Please describe.
Sometimes, schema changes create bugs in the backends as information layout changes and assumptions made on what information looks like are broken.

Describe the solution you'd like
We should aim to add breaking statements when this errors happen, instead of allowing silent exits or wrong output generation. Somehow the backends need to identify that not being able to fetch certain information is not an accident and exit with an error. This is more of a problem in backends/generators. Needs to be relevant to CI tests.

Describe alternatives you've considered
We can follow the "mock DB" approach, and create certain artifacts just for testing, but seems overkill to what we are trying to achieve.