In some projects, I see that a fictitious record is required to create in Db in order to continue the business logic without violating the limitations of Db.
So far I have seen its use in two ways:
- By adding a field of type IsDummy
- Adding a field called ObjectType indicates the type: Dummy
Well, it helps in achieving something.
But what makes me wary of such decisions is sometimes necessary to keep in mind that the application has some kind of dummy records that need to be processed in some processes. If not, you encounter some problems until you realize your existence, or until someone from the team says to you: "Yeah! You forgot the dummy entries. You should also ..."
So the question is:
Is it a good idea to create dummy entries to maintain business logic without making Db complaints? If so, what are the best practices that allow developers to abandon their existence? If not, what do you do to not get into a situation where you have the only option for creating a dummy record?
Thank!