i have a doubt? in which we are setting null if it contains a primary key or act as an primary key, then we cannot set it as null, bcoz its a primary key..so in this case the best option will be On delete cascade Right...
We immediately can know who is a parent and who is a child when we see who has FK on his table, right? FK always has a child, and the parent never can have FK of the child? p.s. What is mean - Cascade?
Spectacular explanation, thank you very much.
Glad it was helpful!
Thank you so much! I finally got what I was looking for..
Thank you so much! I needed this sooo much
From🇰🇷
i have a doubt? in which we are setting null if it contains a primary key or act as an primary key, then we cannot set it as null, bcoz its a primary key..so in this case the best option will be On delete cascade Right...
Thank you for such good explanation
well explained!! THANKS
thank you so much for the explaination
have my interview today (Feb 28 - 2022) at 1 pm at a tech giant. Hope i do well with your video's help
Short and very detailed
Thank you so much!
Thankyou so much😊
Should the on delete cascade constraint be used while creating the table itself??
I think so. Else you need to drop and re add the CONSTRAINT. See this SO answer: stackoverflow.com/a/14182346/8660908
Thanks you for helping
nice explanation
Thanks Maa'm
thanks for ur helping
I have some queries related MySQL , can u help?
thanks .
👍✌️
Hello could you guide me how to set cascade delete for existing table
Thanks
We immediately can know who is a parent and who is a child when we see who has FK on his table, right? FK always has a child, and the parent never can have FK of the child?
p.s. What is mean - Cascade?
Thank you so much! I finally got what I was looking for..
Thanks