Gender can only be male or female is a simple business rule that cannot be captured in an ER diagram. Allowable values for gender are the letters M, m, F, or f. The role of a client in a Civil Action can be either that of plaintiff (represented by the letter P) or defendant (represented by the letter D). An Attorney representing a client should handle the case the client is involved in is an example for a complex business rule that an ER diagram cannot capture. One other thing. Please define Name as the primary key of ATTORNEY.

The purpose of this script is to allow you to concentrate of adding clauses necessary to create the constraints.

a) Create, modify and reorder the create table opportunity statements above to include relevant primary key, not null, check and referential integrity constraints. In other words, at the moment the create table statements are in the following order: the create table statement for the client table comes first followed by the create table statement for the Attorney table, the create table statement for the law_Office table, and the create table statement for the Civil_Action table.

Paragraph The conceptual data model for this scenario expressed using the ER modeling grammar is displayed in the following figure. Addresame Law Office Civil Action Type Location (in Ne_of_mps 11.11 Dole Employs Involved Mandi Dhe Qualtation ION Gene Employee R C R Attorney R. CLIENT Create Tables Opportunity SOL CREATE TABLE chest Clandes char21 C address Gender can only be male or female is a simple business rule that cannot be captured in an ER diagram. Allowable values for gender are the letters 'M', 'm', 'F' or 'T. The role of a client in a Civil Action can be either that of plaintiff (represented by the letter 'P') or defendant (represented by the letter 'D'). "An Attorney representing a client should handle the case the client is involved in" is an example for a complex business rule that an ER diagram cannot capture. One other thing, Please define Name as the primary key of Consult. In order for you to properly define the necessary constraints, you will need to add some additional column names to some of the create tables statements. Essentially what you will be doing is modifying my create table statements so that they include the relevant primary key, not null, check and referential integrity constraints. CREATE TABLE AD ta/50) CREATE TABLEL Office to addres te location char 2030 CREATE TABLE Cction char227) The conceptual data model for this scenario expressed using the ER modeling grammar is dis 1 Address Name num Law Office Civil_Action Tree of case Location status No of_emps Role Employs Involved in Hardles On) Name (0.1) Last nm con First nm Gender Qualification R Lmglave en Address Phones C R name R (0.n) Attorney Esperiente Represen's CLIENT Create Tables Opportunity SQL> ca ge CREATE TABLE client (ci fname varchar2(25), Ci lname varchar2(43), Ci_gender varchar2(1), number(20), Ci address varchar2(60) the At Ci_ph= 15 an Na In CREATE TABLE Attorney (Att name varchar2(60), Att emp varchar2(21). Att qual varchar2(67), smallint COL Att exp na ) wh anc CREATE TABLE Law Office (Lo harne varchar2(45) Lo address varchar2(30). Lo location varchar2(30) CREATE TABLE Civil_Action (Ca_case_num varchar2(27), Ca case type varchar2(21), Ca status varchar2(14)