Laravel 5：使用表单请求同时验证两个字段的问题求助

Hey there! Let’s work through this problem together—you need to validate a form’s time and weekday fields, save them to the schedule table, but block the insert if that exact time + weekday combo already exists in the calendar table. Here are the most solid approaches to make this happen:

Start by adding a check in your backend code right when you process the form request. First, query the calendar table to see if the submitted combo exists:

SELECT COUNT(*) FROM calendar WHERE time = ? AND weekday = ?;

Replace the ? placeholders with the form’s time and weekday values. If the count comes back greater than 0, send a clear error message to the user (like "This time and weekday combination already exists in the calendar—can’t add to schedule") and skip the insert. If it’s 0, run your insert query for the schedule table:

INSERT INTO schedule (time, weekday, [your_other_fields]) VALUES (?, ?, ?);

Heads up: This works for most cases, but watch out for race conditions—if two identical requests hit your server at the same time, both could pass the check before either inserts, leading to unintended duplicates. For full safety, pair this with a database-level guard.

Database constraints or triggers are the most reliable way to block invalid inserts, even with concurrent requests. Here are two options:

2.1 Use a BEFORE INSERT Trigger #

Create a trigger that runs right before any insert into schedule and checks the calendar table. If the combo exists, it’ll throw an error to block the insert:

DELIMITER //
CREATE TRIGGER block_duplicate_calendar_combo
BEFORE INSERT ON schedule
FOR EACH ROW
BEGIN
    DECLARE combo_exists INT;
    SELECT COUNT(*) INTO combo_exists
    FROM calendar
    WHERE time = NEW.time AND weekday = NEW.weekday;
    
    IF combo_exists > 0 THEN
        SIGNAL SQLSTATE '45000' 
        SET MESSAGE_TEXT = 'Time + weekday combo already exists in calendar table';
    END IF;
END //
DELIMITER ;

Make sure your backend code catches this SQL error and translates it into a user-friendly message.

2.2 Atomic Conditional Insert #

Some databases (like MySQL, PostgreSQL) let you do an insert only if a condition is met—this combines the check and insert into a single atomic query, eliminating race conditions entirely:

-- MySQL version (uses DUAL virtual table)
INSERT INTO schedule (time, weekday)
SELECT ?, ?
FROM DUAL
WHERE NOT EXISTS (
    SELECT 1 FROM calendar WHERE time = ? AND weekday = ?
);

-- PostgreSQL version (no need for DUAL)
INSERT INTO schedule (time, weekday)
SELECT ?, ?
WHERE NOT EXISTS (
    SELECT 1 FROM calendar WHERE time = ? AND weekday = ?
);

After running this query, check how many rows were affected. If it’s 0, that means the combo existed in calendar, so you can notify the user.

If you also want to stop duplicate entries within the schedule table (not just duplicates with calendar), add a unique composite index to schedule:

ALTER TABLE schedule ADD UNIQUE KEY unique_schedule_time_weekday (time, weekday);

This will block any duplicate inserts into schedule, even if the combo isn’t in calendar.

Pro Tips #

• Always pair application-level checks with database guards—this gives users immediate feedback and prevents edge-case issues from concurrent requests.
• Keep error messages clear and specific so users know exactly why their submission was rejected.

内容的提问来源于stack exchange，提问作者Downbeat