Database design for fields that should be NOT NULL eventually, but may not yet have a value
Channel: Roel Van de Paar
Date: 2022-09-24

Software Engineering: Database design for fields that should be NOT NULL eventually, but may not yet have a value

Helpful?  Please support me on Patreon: https://www.patreon.com/roelvandepaar

With thanks & praise to God, and with thanks to the many people who have made this project possible! | Content (except music & images) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing | Music: https://www.bensound.com/licensing | Images: https://stocksnap.io/license & others | With thanks to user Will (softwareengineering.stackexchange.com/users/130017), user Newtopian (softwareengineering.stackexchange.com/users/13899), user GrandmasterB (softwareengineering.stackexchange.com/users/897), user Graham (softwareengineering.stackexchange.com/users/25364), user Caleth (softwareengineering.stackexchange.com/users/126524), and the Stack Exchange Network (softwareengineering.stackexchange.com/questions/357799). Trademarks are property of their respective owners. Disclaimer: All information is provided "AS IS" without warranty of any kind. You are responsible for your own actions. Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com