3 ms·
> I would expect the assumption that if the customer doesn't have a fixed contract, they are on a default contract to be encoded in business logic somewhere in
by dahauns 6y ago
> I would expect the assumption that if the customer doesn't have a fixed contract, they are on a default contract to be encoded in business logic somewhere in an application that uses this database.
That's exactly the kind of harmful assumption I'm talking about.
Harmful in that when people act on that assumption and actually implement it that way.
How a default contract might be represented may vary, and of course it is in no way required or even sensible to be stored as a row in the contracts table.
But to think that it is such a fundamentally different kind of data that it should be represented apart from the rest, in a different system, in a different layer, in a completely different form of representation - this is where madness lies.
- pdonis 6y ago> How a default contract might be represented may vary, and of course it is in no way required or even sensible to be stored as a row in the contracts table. But you're saying it does need to be represented somewhere in the database? That putting it anywhere else is harmful? Can you elaborate? Why is it harmful?
- pdonis 6y ago> to think that it is such a fundamentally different kind of data that it should be represented apart from the rest, in a different system The concept of a "contract" is a business logic concept to begin with. That concept is represented in the application already. How (or whether) the data associated with a particular contract is stored in the database is an implementation detail.