The California DMV's completed table diagram is presented in the zyBook. The following is a portion of the table diagram: Vehicle. The SQL below creates the Officer and Event tables. Create the Vehicle and VehicleEvent tables with columns matching the table diagram above and with the appropriate keys and constraints. Some additional notes: All "ID", "Number", and "Code" columns should use unsigned INT data types. All primary keys should auto-increment. The vehicle's model name should be limited to 20 characters.

The C.alifornia DMV's comnleted tahle dianram is nresented in the 7VRonk The followinn is a nortion of the table diagram: The SQL below creates the Officer and Event tables. Create the Vehicle and VehicleEvent tables with columns matching the table diagram above and with the appropriate keys and constraints. Some additional notes: - All "ID", "Number", and "Code" columns should use unsigned INT data types. - All primary keys should auto-increment. - The vehicle's model name should be limited to 20 characters. CREATE TABLE Officer ( OfficerNumber INT UNSIGNED AUTO_INCREMENT, BadgeNumber INT NOT NULL, DepartmentName VARCHAR(30) NOT NULL, FullName VARCHAR(30) NOT NULL, RankCode CHAR(3), PRIMARY KEY (OfficerNumber), UNIQUE (BadgeNumber, DepartmentName) ) CREATE TABLE Event ( EventNumber INT UNSIGNED AUTO_INCREMENT, EventDateTime DATETIME NOT NULL, LocationDesc TEXT(1000) NOT NULL, ReportDesc TEXT(5000), EventCode CHAR(2) NOT NULL, CauseEventNumber INT UNSIGNED, ReportOfficerNumber INT UNSIGNED NOT NULL, PRIMARY KEY (EventNumber), FOREIGN KEY (CauseEventNumber) REFERENCES Event (EventNumber) ON UPDATE SET NULL ON DELETE SET NULL, FOREIGN KEY (ReportOfficerNumber) REFERENCES Officer (OfficerNumber) ON UPDATE RESTRICT ON DELETE RESTRICT )