remove synthetic keys

capriconuser — Wed, 23 Nov 2022 08:36:30 GMT

Anyone please remove synthetic keys from this applcation

Re: remove synthetic keys

hic — Wed, 23 Nov 2022 09:32:20 GMT

Impossible, unless one understands the logic of the data.

But let's make some assumptions, some guesses and ask some questions:

There are a number of cars that are rented. There should be a Car table, with one record per car, and a CarID. Is this the table now called CarRent?
Each car has an owner, and one owner can own several cars. The CarOwner table should contain one record per person, and a field CarOwnerID. The Car table should contain the CarOwnerID.
Each car can be rented multiple times. The Booking table should contain one record per rental occasion, and a BookingID. It should also contain both the CarID and the CustomerID.
The customers are stored in the Customer table. CarOwner and Customer are not the same thing. Then all the links between these two tables must be removed, e.g. LastName cannot be called LastName in both tables.
Each booking can have multiple reviews, stored in the Reviews table. This table should contain the BookingID.

So, remove ALL current keys, and introduce CarOwnerID, CarID, CustomerID, BookingID and ReviewID. No other keys should be present.