Academic degree Essay Example

Academic degree Essay Example Academic degree Essay Academic degree Essay Essay Topic: Academic Therefore the relationship will be M:N legislations. However, the we can use the multivolume attribute to combine all the degrees in to one entity, for instance, we can name the entity as DEGREE and put PhD, Master, and Bachelor in it. One problem we need to consider is that it will be very difficult to count them as all the information are gathered within the same entity. Bert Reply Quote Message unread Set Flag Rave Koran Mallard An employee may have many degrees. Here, employee ID already exists and is a field/attribute in itself. Hobbies requires a new field/attribute and comes under the entity of student details. The relationship is and the model is based on how you build the table. We can create a new table with fields for employee ID and every possible degrees. Here, the primary key of the employed becomes foreign key in the new relation table. But, this model leads many null values which can be still operated. If we use only a field for hobbies we need to assign the text field to contain more than one value. This is called as multivolume attribute. Here, a new schema is created with clear definitions of attributes about what type of attributes can be present and the number of instances of those values ii 1 r more. But still each value in a given value set must be unique without repetitions within the same location. The new schema contains a primary key, which is a combination of the employees (foreign key and unique identification value) and degree(a unique descriptive attribute). New PC pair scheme of employed and individual degrees helps in identifying which degree belongs to which employee and which employee has what degrees. Hide 1 reply RE: week 2 Question 2 Sorry a typing mistake. It is degrees in place of hobbies Reply Quote Delete John Harrington The relationship between Employee and degree is a relationship. An employee could have one or more degrees and different types of degrees such as bachelors, masters, Ph. D, and maybe a JDK could be assigned to one or more employees. It would be best to create an entity for Degree. The primary key from Employee should be used as a foreign key in Degree. Degree should have a key called DE_TYPE that could hold a degree type for each degree that the employee has earned. The Degree table could also be expanded to hold information about where and when a degree was earned. Reply Quote Email Mark as unread Hi John, Your example of degrees with the new attributes of where and when a degree was earned seem to form an interesting combination of multivolume attribute and weak entities. The dredgers is of course a multivolume attribute. The attributes when passed and where studied form weak entities which do not come into picture unless there is a mention of degrees Reply Quote Aisha Cannon The business rule An employee may have many degrees contains two entities which are employee and degrees. This rule translates into a MIN legislations because an employee can earn many degrees and a degree can be earned by many employees. The entity Degrees could be represented by several attributes, including degree type, degree major, degree institution etc. When dealing with multivolume attributes it will be necessary to create several new attributes within the original entity, but be mindful of structural problems in the table and changes in the structure that are made to accommodate modifications. Another solution for multivolume entities is to create a new entity composed of the multivolume attributes components. For example, for the entity degrees the new entity would be degrees major which means a new entity set is composed of a multivolume attributes component. The components would read, health sciences, sociology, criminal justice, human services etc. Reply Quote Email Author Jessica Forbes Aisha agree with your point as to creating a new entity composed of the multivolume attributes components as a solution for multivolume entities. It;s an important point to consider. Reply Quote Email Author Lacer Rancher ERE week 2 Question 2 Having this business rule, an employee may have many degree would quire us to have Non entity: employee and employee_degree. Each one will have primary key and only degree table would have foreign key to link with employee table. In foreign key attribute there should be stored the primary key of employee who has degrees. The relationship would be 1 because an employee can have many degrees. That case we can allow entering multiple records in employee_degree table for each employee and we would not have problem having the redundant data. I hope that does make sense. Nathan Reedy Jammed Hi Lacer Rancher I agree with your post. Altitude attribute is an MIN relationship it will cause the data redundancy so it will affect the integrity of a database. Minored to eliminate we transforming M:N relationship to I:M. Employee table having one unique id and degree table having a same unique id which links employee table. Christopher Reddened The employee to degree relationship is a M:N relationship. Employees can have one or more degrees such as Bachelors, Masters, PH. D. Or MD and each of these degree designations could be assigned to one or more employees. In this scenario it would be most logical to establish an employee primary key ND a foreign key for degree denoting degree type earned for each employee, and en entity for degree. Further information could be denoted in the table regarding types of degrees, when they were earned, etc. Reply Quote Email John Young multivolume attribute is and how it might be implemented. This business rule is an example of when a single attribute is not repeated in a scheme but had multiple values in the same table for it. The difficulty lies in it is now difficult to search the table for a particular degree that a person might have or it is nearly impossible to query an employee and list their ultimate degrees. And so the relationship between employees and degree s is one-to-many, so a primary/foreign key pair needs to be created and a new table. The new table has only one attribute to describe, the degree. In order to specifically identify every row in the table the employee table key (primary key) is needed and the degree table key (primary key) also. So both attributes form the primary key of the two tables. Set Hag James Larceny This rule creates a situation where the attribute is multivolume, an employee may have a bachelors degree in engineering, and other employee may have bachelors degree in engineering also Masters degree in chemistry. This creates the multivolume attribute, and an entity with a MIN relationship, which we know does not work in a relational database. The best way to deal with this issue is to create a new entity made up of the original multivolume attributes. This new entity can also include Associates degrees and Pads, to cover all options. Reply Quote Email Author Bottom Of Form Stephanie Gary James, I definitely agree with your solution here. While itd be fastest for lookup to store each degree as a separate attribute, itd probably be best in this case to rate a new entity that matches each employee to all his degrees. This allows more flexibility in the number of degrees possible. Reply Quote Email Author Emmanuel Addax multivolume attribute is and how it might be implemented. ) The M:N relationship would be in effect for this business rule. Many employees cold have the same degree and more than one degree. Since there are multivolume attributes there may need to be new entities created. The new entity could help specify these types of degree or can be used to specify or quantify the degree or count. Reply Quote Email Author Mike Wagner Jar In the employee and degree relationship the degree cannot exist by itself. The employee and degree exist in many to many relationship. There is a possibility that this could cost some redundancy. That is the one thing that you dont want if it can be avoided is redundancy. Reply Quote Email Author The rule that an employee may have many degrees calls for there to be a 1 relationship between the person and the degree(s) theyve attained. This can be done with only three fields as pictured below but this doesnt allow effortless searching based on the degree due to the degree field containing ultimate degrees.