✅ 𝗙𝗶𝘅𝗲𝗱 𝗮 𝗙𝗼𝗿𝗲𝗶𝗴𝗻 𝗞𝗲𝘆 𝗖𝗼𝗻𝘀𝘁𝗿𝗮𝗶𝗻𝘁 𝗘𝗿𝗿𝗼𝗿 𝗶𝗻 𝗔𝗦𝗣.𝗡𝗘𝗧 𝗖𝗼𝗿𝗲 (𝗘𝗙 𝗖𝗼𝗿𝗲)

Today, I worked on resolving a common database error when saving related data in the wrong order.

🔍 𝗜𝘀𝘀𝘂𝗲:

𝗥𝗲𝘀𝘂𝗺𝗲𝗙𝗶𝗹𝗲 𝗵𝗮𝘀 𝗮 𝗳𝗼𝗿𝗲𝗶𝗴𝗻 𝗸𝗲𝘆 𝘁𝗼 𝗝𝗼𝗯𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻.

𝗜 𝘄𝗮𝘀 𝘀𝗮𝘃𝗶𝗻𝗴 𝗥𝗲𝘀𝘂𝗺𝗲𝗙𝗶𝗹𝗲 𝗳𝗶𝗿𝘀𝘁 — 𝗯𝘂𝘁 𝗝𝗼𝗯𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗱𝗶𝗱𝗻’𝘁 𝗲𝘅𝗶𝘀𝘁 𝘆𝗲𝘁, 𝘄𝗵𝗶𝗰𝗵 𝗰𝗮𝘂𝘀𝗲𝗱 𝗮 𝗳𝗼𝗿𝗲𝗶𝗴𝗻 𝗸𝗲𝘆 𝗰𝗼𝗻𝘀𝘁𝗿𝗮𝗶𝗻𝘁 𝗲𝗿𝗿𝗼𝗿.

🛠 𝗙𝗶𝘅 (𝗦𝘁𝗲𝗽𝘀):

1. Made JobApplicationId nullable in ResumeFile model.

public int? JobApplicationId { get; set; }

1. 𝗦𝗮𝘃𝗲𝗱 𝗥𝗲𝘀𝘂𝗺𝗲𝗙𝗶𝗹𝗲 without setting JobApplicationId:

_unitOfWork.ResumeFile.Add(resumeFile);

_unitOfWork.Save();

1. 𝗦𝗮𝘃𝗲𝗱 𝗝𝗼𝗯𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 and used the generated ID:

_unitOfWork.JobApplication.Add(jobApplication);

_unitOfWork.Save();

1. 𝗨𝗽𝗱𝗮𝘁𝗲𝗱 𝗥𝗲𝘀𝘂𝗺𝗲𝗙𝗶𝗹𝗲 𝘄𝗶𝘁𝗵 𝗝𝗼𝗯𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝗜𝗱:

resumeFile.JobApplicationId = jobApplication.Id;

_unitOfWork.ResumeFile.Update(resumeFile);

_unitOfWork.Save();

📌 𝗟𝗲𝘀𝘀𝗼𝗻: 𝗦𝗮𝘃𝗲 𝗽𝗮𝗿𝗲𝗻𝘁 𝗿𝗲𝗰𝗼𝗿𝗱𝘀 𝗳𝗶𝗿𝘀𝘁 𝗶𝗳 𝗳𝗼𝗿𝗲𝗶𝗴𝗻 𝗸𝗲𝘆 𝗰𝗼𝗻𝘀𝘁𝗿𝗮𝗶𝗻𝘁𝘀 𝗲𝘅𝗶𝘀𝘁 — 𝗼𝗿 𝗺𝗮𝗸𝗲 𝘁𝗵𝗲 𝗙𝗞 𝗻𝘂𝗹𝗹𝗮𝗯𝗹𝗲 𝗮𝗻𝗱 𝘂𝗽𝗱𝗮𝘁𝗲 𝗶𝘁 𝗹𝗮𝘁𝗲𝗿.

💬 𝗛𝗼𝘄 𝗱𝗼 𝘆𝗼𝘂 𝗵𝗮𝗻𝗱𝗹𝗲 𝘀𝗮𝘃𝗶𝗻𝗴 𝗿𝗲𝗹𝗮𝘁𝗲𝗱 𝗲𝗻𝘁𝗶𝘁𝗶𝗲𝘀 𝘄𝗶𝘁𝗵 𝗳𝗼𝗿𝗲𝗶𝗴𝗻 𝗸𝗲𝘆𝘀 𝗶𝗻 𝗘𝗙 𝗖𝗼𝗿𝗲? 𝗔𝗻𝘆 𝘁𝗶𝗽𝘀 𝗼𝗿 𝗯𝗲𝘀𝘁 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀?