| | |
DataBase Design Help
Please support our Database Design advertiser: PostgreSQL or MySQL? Compare and contrast the two most popular open source databases
Thread Solved |
•
•
Join Date: Aug 2008
Posts: 1,162
Reputation:
Solved Threads: 138
I will help, not do assignments, what specific pieces are you having trouble with?
Also what is background and skills in the volunteers table?
One more, where did the relationships table go? ClientChild table means only children and not other relationships? Client table has a next of kin column, what is this?
Also what is background and skills in the volunteers table?
One more, where did the relationships table go? ClientChild table means only children and not other relationships? Client table has a next of kin column, what is this?
Custom Application & Software Development
www.houseshark.net
www.houseshark.net
•
•
Join Date: Aug 2008
Posts: 1,162
Reputation:
Solved Threads: 138
i agree, would also add clientpets to bookings / volunteers
Custom Application & Software Development
www.houseshark.net
www.houseshark.net
•
•
Join Date: Oct 2008
Posts: 15
Reputation:
Solved Threads: 0
Next Stage is covert the relational model into object oriented shema
I need help converting a relational model into an object-oriented database design in terms of classes, listing all attributes for each class together with their reference and collection data types.
Entities
Entity
Booking
Attributes
bookID (Pk)
volServID (Fk)
clientID (Fk)
Date-Req,
Hours_Req
Entity
Client
Attributes
ClientNo (Pk)
ClientName
ClientType
ClientAddress
ClientTel
NextOfKin
Entity
Volunteers
Attributes
volNo (Pk)
volName
volTel
volAddress
AreaofSpeciality
Entity
Volunteer_Services
Attributes
Vol_ServNo
serviceNo (Fk)
volNo (Fk)
track
Entity
Service
Attributes
serviceNo (Pk)
serviceName
Entity
Client_Pet
Attributes
PetNo (Pk)
PetName
Description
Client_No(FK)
Entity
Client_Child
Attributes
ChildNo (Pk)
ChuldName
DateOfBirth
Sex
Client_No(FK)
I need help converting a relational model into an object-oriented database design in terms of classes, listing all attributes for each class together with their reference and collection data types.
Entities
Entity
Booking
Attributes
bookID (Pk)
volServID (Fk)
clientID (Fk)
Date-Req,
Hours_Req
Entity
Client
Attributes
ClientNo (Pk)
ClientName
ClientType
ClientAddress
ClientTel
NextOfKin
Entity
Volunteers
Attributes
volNo (Pk)
volName
volTel
volAddress
AreaofSpeciality
Entity
Volunteer_Services
Attributes
Vol_ServNo
serviceNo (Fk)
volNo (Fk)
track
Entity
Service
Attributes
serviceNo (Pk)
serviceName
Entity
Client_Pet
Attributes
PetNo (Pk)
PetName
Description
Client_No(FK)
Entity
Client_Child
Attributes
ChildNo (Pk)
ChuldName
DateOfBirth
Sex
Client_No(FK)
![]() |
Similar Threads
- your ideas on database design??? (Database Design)
- Database design regarding two 'linking' tables (Database Design)
- Database Design for storing versions (Database Design)
- Database Design feedback (absolute beginner here :) (Database Design)
- Help with contact/mailing list database design... (Database Design)
- Database design - subtypes and instances of an entity (Database Design)
- Database Design - Supertypes and Subtypes (Database Design)
- Database Design Advice (MySQL)
Other Threads in the Database Design Forum
- Previous Thread: Object-oriented database design
- Next Thread: Help defining relationship
Views: 1465 | Replies: 13
| Thread Tools | Search this Thread |
Tag cloud for Database Design






