It's UWAweek 16 (1st semester, week 7)

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 selected article
Showing 1 of 89 articles.
Currently 1 other person reading this forum.


 UWA week 15 (1st semester, week 6) ↓
SVG not supported

Login to reply

👍?
helpful
2:06pm Sat 13th Apr, Maira A.

Hi, Check this : [help1402] ANONYMOUS wrote:
> G'day Professor, > There is two CONSTRAINTs that make me very confused on what should I done with it: > > A: ONLY 1 SURGEON(=1 Appointment) IN 1 ROOM IN 1 DATE_HOUR : > Please note that more than one surgeon can use the same room at different > times. However, a surgeon will only use one room at a time > > B: PATIENT can ONLY BOOK 1 SURGEON IN 1 DATE(of Appointment entity) > The patient is allowed to schedule appointments with different surgeons on the same day if needed. However, the patient cannot have multiple appointments with the same surgeon on the same day > > > AT first, I using relationship to build this constraint but I couldnt find a way to do it. So I build 2 entities as schedule tables of surgeons and of the rooms. But when I went to the lab, I got a feedback that I have too many entities (Which I think maybe I does). So I when back and try do find another solution, but it took hours and to me, unless we can use foreign keys (Which is not yet), there is no other solution to me. So I confusing right now that should I just skip it and let the foreign keys do the job or should I just let those 2 entities as solution. > > > The Lab assitant is very great with help but the feedback in this is really made me confused, so can you please give some feedback about this. Thank you very much for your time.

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  5:07AM Sep 06 2023
Privacy policy