I'm told that this is not a good design to allow tap in area definitions ... I know that It can cause errors. ..but please someone please explain and explain in which situation should I not allow tap and why the theory is, what is the best practice? I want to understand.
Edit
My dilemma is that I will have to change the DB now, and the code will be implemented later ... so I'm worried about the new field field and tap Non-field-specific INSERT statements do not pose a risk. This is the area where I am not clear. I want to allow zero because I think it is less risky, but others have told me that this is a bad design. In this phase I am more concerned about reducing the risk when the code is implemented. I would be happy if someone would help me clarify my choice, I lack confidence and I need to make a decision soon.
This is very simple, in many cases you do not know - for example - if a person has children NumberOfChilds = 0 means: he has zero children, zero meaning: you do not know.
But if you can make the information compulsory in the whole process, it would be good to implement it at the deepest level.
Allow the customers to tap your logic and tap the non-null-field marked with '1 child' is better, to indicate that "do not know yet" if you If you take the amount then you are lost or everyone opens their secret code to patch their system.
Comments
Post a Comment