Yes and no. I am not the biggest fan of dummy objects, as it can lead to accidental errors as well if somebody removes/changes it in the db, but on the other hand, it would enable us to not have null checks...
Sure, it can be the same class just a different named constructor for instance. To make sure that all values are set properly can be enforced via Test case. Happy to merge this as is though.
Yes and no. I am not the biggest fan of dummy objects, as it can lead to accidental errors as well if somebody removes/changes it in the db, but on the other hand, it would enable us to not have null checks...