Domain Modelling ! %#& ' ! " # $ 7&$& ' 89 8 : & $&$*% ; --- ! " #$%&'$& %%( #) ((*+ & %'%, - % ',%% % ( $. / $0') % %(%- #% $((%'% 0, 0%%&& $'% (,% -

Transcriptie

1 ! " #$%&'$& %%( #) ((*+ & %'%, % ',%% % ( $. / $0') % %(% #% $((%'% 0, 0%%&& $'% (,%,, & % ) #$ (#$ 0 %$# ) (') ) %# ) ) ) ) #,%'$%, 0 # % %!, & % % 1$. / $%#$ # ) % $ & %( #%) %((*, 2)))3) #4# ( 5547!! " # $ nr wk ma do Thema Casus closer to the user B SQL (1) Opstellen datamodel Modelling B SQL (2) B Data transformatie B4 B SQL (3) Toets B Mapping/constraints/SQL At the end: SQLknowledge required Transformation more technical 7! %#& ' * $ 7&$& ' 89 8 : & $&$*% ; 1

2 ( 1 &( $ %* %($ ) *0$ ) %$ % % $%" $ = $ * * ( & % 0% ) * > 1$ 0* * % ) $? (@ % * $% % ;& ) *+, ) * ) #% $ &(? ( * %(@A BC = 0 % % $ &( $ $ 9! :%("* *0 9! ":& & * % 1 * (*,%;& $ > %# <! #& '(' 1$ % *& %( &% 1 & E $ *%("* 0) &( ; 4:F * * 9 # * #E: := $&($! :& %$ $ 9 ':$ (:#*?*%) * D G %#% * $)( %. %) $&% 0%&&*# * 9# *((:$%%$% / $&&* ( * ( ( * ((( 0 %) $ &(( %% $% % & #%# * $% % * $ ( %(*$ " & H ),* &#%*&& 1I =F 9 & # %% : H 1 2 ),* && 1I =F #)$#$%% $#)0&& & $& 45 3 #& '/4 578!79 : 8"; % "% B8 J! 1I % %"*& %"% % " "%" % " "% B8J I 1I 8 8.9%";& : ; & 8 J! 1I 81KI! 8 94: L=?AAA@ = 1I 9?$@0? (@0?%@0?! % %@0?I J $ &( J! 1I " domainconstraintdefinition DROP CONSTRAINT constraint 44 3 #& '/4 578!78##7!"9 ; ; & 8 1J I 8 8.9%";& : 4 %& ( %% 8 1J I I J M19 8NLJ! F G B?%@I 8*OC?%@:: I $& $) $ $ J I I J M19 8NLJ! F0F G FFI J BFFI J I 9FG $N F *:C5555:: J $ &( J F 1J I 1 && %(*$! 0$& *( ( %(* " 4 2

3 5 3 #& '/ 4 (( +578! 7! 8 '7( 3((( 4 (( +( <(( ( ("(" "% *$) 4%%*% * % 7S$ T% %%*$ PF1! K. KQ= I 1 = R9 " : (( $#9%*:& ** $ & & ** %(I J I = $ %(* ( (() $# > % $# %%*9*$& **: ((4 9S *T: $*; &#) =9 7"; >7?3( 4( $? "%@$ 7=77; 57# ("(9 " : 9 ; 7'7!7 PI J 81J I Q88 Q L=Q I =R 9 PI J 81J I Q88 Q L=Q I =R ("(" QJ F8J I 1I P 18Q88 R 4 8 B? { } P from /has Player is captain of plays in X Team (Teamname) plays in Class heeft is trainer of relational mapping (possibility 1) : team ( teamname, firstname, surname, class ) ( ) player ( firstname, surname, teamname ) trainers ( firstname, surname, teamname ) x 4U! #& '' CREATE table Team ( Teamname Plays_in_class smallint CHECK ( Plays_in_class between 1 and 4 ), primary key ( Teamname ) unique (, ) ) CREATE table Player ( Plays_in_Team primary key (, ) ) CREATE table Trainers ( Teamname primary key (,, Teamname ) ) ALTER table Trainers ADD foreign key (Teamname) references Team ( Teamname) ALTER table Trainers ADD foreign key (, ) references Player (, ) ALTER table Player ADD foreign key (Plays_in_Team) references Team (Teamname) CREATE ASSERTION captainplaysinownteam CHECK ( not exists ( select * from Team X where exists (select * from Player Y where X. = Y. and X. = Y. and X.Teamname = Y.Plays_in_Team))) 4< 8 B#& ''3 )B *4 Movie (nr) Title was directed by/ directed has was reviewed by/ reviewed Person Country & ) $% % #$ # ($ #) $ #V was born in Person Rmapping ( personname, birthcountry) Movie ( movienr, title, director ) Reviewed ( personname, movienr ) J )%7& ** %7 *% $9 &:B ( & %(*$) "?$@ CREATE assertion CHECK ( not exists ( select * from Movie natural join Reviewed If assertions are not supported by the RDBMS, the exclusion constraint maybe can where director = personname) ) be enforced by insert and update triggers. 4D X 3

4 0( w 8 >#$ &(* $ $ & $ w % %% '0 #(*&%44 &&0 0 % w %%%;0 &! 5 #& ' # %( %*& * (& %(* $ '% % & #% Format 1 for granting privileges on tables and views Format 2 of the GRANT command is used to grant special privileges to other users. In order to use format 2 of the GRANT command, you must have DBA Authority. $*; $ $/ I % GRANT { CONNECT TO listofusers [ IDENTIFIED BY pswrdlist ] DBA TO listofusers [ IDENTIFIED BY pswrdlist] SCHEDULE TO listofusers [ IDENTIFIED BY pswrdlist ] RESOURCE TO listofusers } $ *; $? 4@ grant all privileges select insert [(col)] update [(col)] delete usage... on object to userlist [ with grant option ] #& ' 34 The listofprivileges (of format 1) that can be granted is: A! C 8 M M 1I M M M M For instance: =F 9 " ": M M GRANT UPDATE ( NR_CHILDREN ), SELECT ON PRES_MARRIAGE 1I M M TO REAGAN M WITH GRANT OPTION 5 B 5 DE 1?% %(& #% ; %*0( %0% %% Commit Work <==> Rollback Work $$ $%(%#*! *! $#$)? %@ %) $$ $? % 9L 4:& # *( ) $$ revoke [ grant option for ] privilegelist on object from userlist [ restrict cascade ] AUTOCOMMIT ON # * %$ % $& #* % %$ $# * % 0%$) $#$& J 8.G J.%* =/ 9L #&& #: REVOKE { DBA CONNECT RESOURCE SCHEDULE } FROM listofusers 7 AUTOCOMMIT OFF! %( %*& 8J!! 1G J. %$% ) % ) 0) $$ ;% 0%(? %@? %(@ 4

5 ( )* $(! %# (&%$%( : 0$ 0 $* ) * $?@"% #3&%$) * %0$ ) ( = Consider the following situation: Student (studentnr) Student PK Studentnr Name has Course PK Course code Lecturer Course...for...got... VisioModeler result: Name has Rating Results PK,FK Studentnr PK,FK Course code Rating { '1'.. '10' } Rmapping Lecturer Make names more readable : Student PK Student studentnr Name Course PK Course code Lecturer name Student (studentnr, name ) (1..10) Results (studentnr, code, rating ) Course (coursecode, lecturer) has / is of has / is of Student Course got Rating PK,FK Student studentnr PK,FK Course code Got Rating < : # 8 ( VisioModeler generated as MS Access (3.x) databasestucture: (Of course: also without generating a database, it is possible to lay down the necessary primary and foreign keys, validation rules etc..) Opening the Resultstable in Designview gives the next picture: As you can see in this second picture, something went wrong with the datatypes: Rating got the default type char(10) and therefore also the validation rule became somewhat strange... Better is: before you generate the databasestructure, design inside the VisioModelertool aspects of the Physical Model! D A In the physical design step we transform the general logical model to a model appropriate for a certain databasesystem (like MS Access). In this way, we can make use of the distinct possibilities [like data types] that a certain RDBMS can offer us. So for instance for the Rating value type we can activate the Object Type Properties window (see aside) and change the default value of text(10) to numeric (or to text(3) if you may want so). After generating a new database (with this Numeric data type, we will find that indeed in the MS Access database the Ratingfield has the numeric data type and the validation rule is now: Between 1 And 10 (so no quotes anymore around 1 and 10 ). So: do this (re)definitions of data types etc. before generating the database... W! 5

6 #& ': 34 * * * ( $% ($%($ 90((0 #) 0% 0 0%& #: = ) $$* ( *> *$ 9,$&&(: "# ; & : #(8 $#$) <9?#@:* ( MSysObjects, MSysACEs, MSysQueries, MSysRelationships, MSysAccessObjects, MSysIMEXColumns, MSysIMEXSpecs ) 0$ %* # * *! $> * SELECT * from MSysObjects $L ( %" " # 7* ( 74 7#& ' 1 *97 % :& # 9 %080 8(0L 0F0:&(%9 (%: " )$! &) $ " 1 ) * (&(& $! "$ " 1 ) * " 0$#$ ;%% # $?%(@ $! 1 $$*;S M 8 T M 8 LJ! %G % B47X " 1 ) * (&( () $"" (,3# (%#$! "( L %*0 ( %X455$? #@$$* $# ) $%(% &$%0;$5@ # 9 " 0) $ 8 0J F I %L 8 "& J && VŁ 1! "&(; %* & :; W Study the content of these sheets (/handout) If necessary: study the content of the PDFfile Db schema transformation and optimization.pdf, page 17. Bij exercise 8.b (over de Landencompetitie worstelen ) heb je bij de onderdelen a.2, b.2 en c.2 (waarschijnlijk) drie verschillende relationele tabelstructuren gevonden. a) Transformeer voor elk van die verschillende databasestructuren de gevonden beperkingsregels nu naar SQLopdrachten, waardoor het mogelijk wordt om alle constraints te bewaken en ervoor te zorgen dat de integriteit van elk van die (drie verschillende) databases bewaakt blijft. Zorg ervoor, dat de integriteitsbewaking via SQLDDL of anderssoortige commando s volledig is! b) Geef aan de hand van de complexiteit en omvang van de benodigde constraintbewaking aan, welk van de drie structuren je voorkeur verdient (met andere woorden: in welk geval kost het het minste en/of gemakkelijkste programmeerwerk?). Opmerkingen: Gebruik als criteria voor de van toepassing zijnde beperkingsregels de populatie van de voor deze opgave gegeven tabelvulling. Het systeem wordt daardoor weliswaar dichtgetimmerd (d.w.z. je kunt er helemaal geen gegevens aan toevoegen of eruit verwijderen etc.), maar het gaat hier om het oefenen in databaseconstraintbewaking! Let erop, dat àls je de Visiomodelercasetool gebruikt, deze tool de complexe beperkingsregels van dit Landencompetitie worstelen voorbeeld misschien nìet allemaal en niet helemaal correct kan verwerken! Je zult dus handmatig moeten controleren hoe alle beperkingsregels uit het CS correct getransformeerd moeten worden tot databaseconstraints! 7B F 2. $) 8 %) $ && Sex & && # (* PhoneNr 98B#0 B#0 FB&*$ :0% $ & # % is of <= 2 uses Applicant : & $ 8 (:J & ' $& $ : & * & '% & $ %:/ # " %(% %" * $$ 3...for...obtained... undertook Ability...for...took......on...got... { 'C, A, P' } Task Score (nr) { '1'.. '100' } Period (h) Rating { ''A'.. 'D'' } 7 7U