It looks like you’re new here. To join in the discussion, click the register link below to get started.
In this case I think a NOT NULL constraint is completely reasonable, sounds like a required field from where I am sitting.thecraicbear said:Good to know, thank you!
For more info behind the field, it accepts a 1 or a 0 (BIT) for yes or no, as to whether or not somebody has an embargo on their account.
Agreed, not only can you not rely on good data being passed, I treat all data as potentially harmful until validated. Either thru maliciousness or negligence. Basically the ol' Little Bobby Tables principal: https://www.xkcd.com/327/Operator1 said:
Often, you can't rely on all callers to consistently pass good data to you, so contingencies like constraints & default values help you keep your data clean no matter how sloppy front-end apps and/or users are.