Any thoughts on whether a table design like this is smart and if we'll run into problems later if we have many users or cars? The system will need to let users search available cars in a certain time slot quickly.
Cars can only be reserved in half hour chunks in case this information can be used for a smarter db design. Thanks for any feedback.
The design itself should be ok, assuming more columns or tables with more details will be added.
e.g.: If you get more and more cars, they might get the same title,
or users could have the same email address (family situation where husband or wife both use the system).
The id (assuming it's a serial) will not give you the information you need if two cars with the same title are standing next to eachother.
Also, the locations where the cars are picked up or are left behind could be usefull, maybe cell phone numbers if the guy driving the car before you is late, you can find out if he's going to be WAAAY late or just a few minutes.