The goal of this project is to create a system for managing different types of vehicles, such as cars, trucks, and motorcycles. To achieve this, we will model the features and behaviors of these vehicles. The first step is to create an abstract class called Vehicle, which will contain properties and methods that are common to all vehicles. These properties include make (brand), model, speed, and maximum speed. The methods will include accelerate, decelerate, and showinfo. Next, we will create an interface called Idrivable, which will define the drivability characteristics of the vehicles. This interface will have methods for starting and stopping the vehicle. For the Car class, we will create a class that is derived from the Vehicle class and also implements the Idrivable interface. In addition to the properties and methods inherited from the Vehicle class, the Car class will have an additional property for the number of doors. We will also override any necessary methods and implement the methods from the Idrivable interface. Similarly, for the Truck class, we will create a class that is derived from the Vehicle class and implements the Idrivable interface. This class will have an additional property for the load capacity. Again, we will override necessary methods and implement the Idrivable methods. For the Motorcycle class, we will follow the same approach as the Car and Truck classes. This class will have an additional feature for the type of motorcycle (sport, cruiser, etc.). In all classes, we will set the access modifiers (private, protected, public) for properties and methods accordingly. In addition to the above, you have mentioned adding an order check in the order class. It is important to have a clear understanding of the purpose and functionality of this check before implementing it. One possible approach could be to create a method in the order class that checks for the existence of payment and cancels the order if payment does not exist. However, this is just one suggestion and the best approach will depend on the specific requirements of your project. It is important to thoroughly plan and test any new features before implementing them.

Right now it’s working fine, but this does not feel like it’s the right way to do it. The Profielfoto is the only value that is nullable, also in the database. This is the script right now, I check if the value is null and I do the same script twice, the only difference is the image:

i am trying to send data to the db but i keep running into this exception