C
C#•3w ago
Faker

✅ Logic to choose different context from database in code

Hello guys, I have set up a database that has tables Instructor and Student. The thing is, both Student and Instructor have same properties and I need to perform CRUD Operations. This mean, the logic of the code remain the same, only the context will change each time. My question is: 1. Do I implement an if statement logic to check whether we are interacting with instructor or student, then depending on that use appropriate context OR 2. I declare 2 different class, one for StudentOperations and another for InstructorOperations? But while doing so, don't we repeat the codes? 3. Can an interface be helpful here? I was thinking of implementing an interface to define the CRUD methods, but what's the point here?
3 Replies
Faker
FakerOP•3w ago
C#
public void DeleteUser()
    {
        // Delete by email
        string? email;
        while (true)
        {
            Console.Write("Please enter the email of the student you want to delete: ");
            email = Console.ReadLine();
            if (Validations.ValidateString(email))
            {
                if (Validations.ValidateEmail(email))
                {
                    if (Validations.CheckEmailExistence(email))
                    {
                        break;
                    }
                    Console.WriteLine("Email not found, please re-input.");
                }
                else
                {
                    Console.WriteLine("Wrong email format; format should be in the form John.Doe@example.com, please re-input.");
                }
            }
            else
            {
                Console.WriteLine("Email can't be empty, please re-input.");
            }
        }
        try
        {
            using (var context = new DrivingLessonBookingSystemContext())
            {
                context.Students.Where(s => s.Email == email).ExecuteDelete();
                Console.WriteLine("Student deleted successfully.");
            }
        }
        catch (Exception e)
        {
            Console.WriteLine($"Processing failed: {e.Message}");
        }
    }
C#
public void DeleteUser()
    {
        // Delete by email
        string? email;
        while (true)
        {
            Console.Write("Please enter the email of the student you want to delete: ");
            email = Console.ReadLine();
            if (Validations.ValidateString(email))
            {
                if (Validations.ValidateEmail(email))
                {
                    if (Validations.CheckEmailExistence(email))
                    {
                        break;
                    }
                    Console.WriteLine("Email not found, please re-input.");
                }
                else
                {
                    Console.WriteLine("Wrong email format; format should be in the form John.Doe@example.com, please re-input.");
                }
            }
            else
            {
                Console.WriteLine("Email can't be empty, please re-input.");
            }
        }
        try
        {
            using (var context = new DrivingLessonBookingSystemContext())
            {
                context.Students.Where(s => s.Email == email).ExecuteDelete();
                Console.WriteLine("Student deleted successfully.");
            }
        }
        catch (Exception e)
        {
            Console.WriteLine($"Processing failed: {e.Message}");
        }
    }
For example say I have this, the only thing that changes is the context.Students instead of students, we would have instructors
Salman
Salman•3w ago
In my opinion, it's better to keep them organized, there should be separate services for both of them because they might have same properties for now but what if later on they grow and have different props and functions Perhaps using the same function for two different tables also violates the single responsibility principle and might mess things up
Faker
FakerOP•3w ago
Hmm yeah it might be better to just separate them into 2 distinct classes I have a question, I need to perform CRUD operations on both entities, is it a good idea to create an interface? I don't really see why we would need an interface here beside just ensuring that each class has the exact same method but with different implementation. When/why would we need interfaces please, any case-scenario? I'm just experimenting with interfaces, that's why I just created one

Did you find this page helpful?