It's UWAweek 42 (2nd semester, week 12)

help1402

This forum is provided to promote discussion amongst students enrolled in CITS1402 Relational Database Management Systems.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 3 articles in this topic
Showing 3 of 612 articles.
Currently 119 other people reading this forum.


 UWA week 39 (2nd semester, week 9) ↓
SVG not supported

Login to reply

👍x1
helpful
12:39pm Fri 27th Sep, Liang Y.

Good day, I would need some clarification on PK for HiredVechicles. If we use Date as PK, we are unable to uniquely identify the hired vehicles as we will rent out multiple of cars at the same day. Should use a composite PK to uniquely identify each tuple/row? Cheers


 UWA week 40 (2nd semester, week 10) ↓
SVG not supported

Login to reply

👍x1
helpful
3:25pm Mon 30th Sep, Mehwish N.

Date and ClientID, together may work, but you can also create a new ID attribute.


SVG not supported

Login to reply

👍?
helpful
10:19am Thu 3rd Oct, Adam W.

I would suggest that in the case of a natural key not being able to be used (like the example mentioned about multiple cars at the same time for the same client), you would create a surrogate primary key, such as HireID etc. "Liang Yap" <24*3*9*6@s*u*e*t*u*a*e*u*a*> wrote:
> Good day, > > I would need some clarification on PK for HiredVechicles. > > If we use Date as PK, we are unable to uniquely identify the hired vehicles as we will rent out multiple of cars at the same day. > > Should use a composite PK to uniquely identify each tuple/row? > > > Cheers

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy