How to design a persistent table with dependencies which are allowed to be deleted in the future?
Channel: Roel Van de Paar
Date: 2021-09-20

How to design a persistent table with dependencies which are allowed to be deleted in the future?

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 Scott Hodgin - Retired (dba.stackexchange.com/users/60085), user grustamli (dba.stackexchange.com/users/179200), and the Stack Exchange Network (dba.stackexchange.com/questions/236780). 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