It's UWAweek 47

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 684 articles.
Currently 123 other people reading this forum.


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

Login to reply

👍?
helpful
7:52pm Tue 24th Sep, ANONYMOUS

For part 2 of the project, are we allowed to add/change the PK or are we just supposed to follow what was given in the ERD provided?


SVG not supported

Login to reply

👍?
helpful
10:59pm Tue 24th Sep, ANONYMOUS

When considering the ERD provided, it is really difficult to understand the path of the arrow. Can you clearly give the path? As an example HiredVehicle - Invoice relationship, it is really difficult to understand the path of the arrow. I think this would be the answer for many students questions regarding ERD. Thanks.


SVG not supported

Login to reply

👍?
helpful
11:16pm Wed 25th Sep, ANONYMOUS

Hi, I think you can easily infer the direction of the arrow based on the text. For Invoice it is Invoice --- generated for ---> HiredVehicle It is mentioned in this narration "Only after the vehicle is returned an invoice is generated for the vehicle hired" in the case study part. So I think if you get a bit confused by the direction of the arrow you can just read over the narration again. Or maybe you can also use common logic to infer the direction? For example I think HiredVehicle --- generated for ---> Invoice sounds a little bit weird. Because usually it is invoice which is generated for an order. Not the other way (generating order for an invoice). Hope this helps.

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