Knowledge

Relational Model/Tasmania

Source ๐Ÿ“

22: 172:
Following a disappointing uptake of RM/T by the database industry, Codd decided to introduce the RM/T model more gradually. He planned to release a sequence of RM versions: RM/V2, RM/V3 etc. each time progressively including some of the ideas of the original RM/T into the new version. Perhaps this
149:
Between 1968 and 1988 Codd published over 30 papers on the relational model (RM) - the most famous of which is his 1970 paper. Up to 1978 the papers describe RM Version 1 (RM/V1). In early 1979 Codd first presented some new ideas, called RM/T ('T' for Tasmania), at an invited talk for the
799:
There is little mention of RM/T today and no articles have appeared recently. Peckam and Maryanski (1988) wrote about RM/T in their study of semantic data models. Codd published his book in 1990 but wrote nothing more about RM/T. RM/V1 and RM/V2 have a chapter each in
181:
entity types in Codd's 1990 book that defines RM/V2. On the other hand, the book extends and builds on the existing body of query language issues, many of which were addressed by Codd in several papers throughout the 1980s.
141:. Codd writes: "the result is a model with a richer variety of objects than the original relational model, additional insert-update-delete rules and some additional operators that make the algebra more powerful." 169:. Although Codd writes nothing about this new type, Date offers a rationale in Date (1983, page 262). Date revised this 1983 article in Date (1995), which additionally compares the RM/T model with the E/R model. 804:(1992) and the Date (1983) article was updated in (1995) and now contains a long overdue comparison of the E/R model and RM/T. Date's most recent reflections can be found on the Web at Date (1999), 410:. However Codd does not define a notation for diagramming his new semantics. Each entity may play several roles at once and thus belong to one or more of the following entity types: 479:
relationship between two independent entities. For example, a writer may write many books, hence a one-to-many relationship between writer and book entities; the book is the
823:
and continues to influence new data modellers. See the paper by Hammer and McLeod (1981), the book by Knoenke (2001) and implementation by Grabczewski et alia (2004).
820: 158:, Tasmania. Later that year the ACM journal published a paper on RM/T, in which Codd acknowledges the influence of Schmid & Swensen (1975) and Wiederhold (1977). 201:
is a unique value assigned to each entity. If two relations use the same surrogate value then they represent the same entity in the modelled universe. The surrogate
1052: 532:
is used when deleteting entities from the RM/T model; all associations that have surrogates referring to a non-existing entity are assigned the value
205:
can be any unique string or number but cannot be assigned or changed by the database user. For example, a SQL SEQUENCE is often used to generate
86: 406:
semantics by taking the original RM and categorising the relations into several entity types, increasing the information captured by the
58: 39: 664:
The Catalog is a meta-model storing the descriptions of the relations themselves. The RM/T Catalog comprises the following relations:
65: 72: 54: 105: 173:
explains why there is no obvious mapping of concepts between RM/T and RM/V2. For example, there is no reference to
584:
relations are defined to capture further semantic features of the RM/T model. These graphs are named as follows:
1112: 1041: 1022: 990: 971: 43: 339:
is a relation (table) storing the surrogate and one or more attributes of an entity. The surrogate value of a
491:
entity contains at least two designations. For example, we can regard a booking as either an entity that
79: 873:
Hall, P. A. V.; Owlett, J.; Todd, S. J. P. (1976). "Relations and Entities". In Nijssen, G. M. (ed.).
900: 355:"Employee_Number" is a table with two columns: one containing the surrogate value of the "Employee" 32: 1191: 816: 209:
surrogate values. This use of surrogate was first introduced in Hall, Owlett and Todd in 1976.
1158:
Proceedings of the 1975 ACM SIGMOD international conference on Management of data - SIGMOD '75
165:
in Date (1983) in which Date and Codd improved and refined RM/T, adding an entity type called
241:
entity has a surrogate but it belongs to another entity, i.e. the surrogate is a foreign key.
790:
Numerous operators are defined on names, sets and graphs. See Codd's 1979 paper for details.
435:
Codd goes on to introduce subtyping of entities, giving yet another qualifier for entities:
893: 8: 407: 1156:
Schmid, H. A.; Swensen, J. R. (1975). "On the semantics of the relational data model".
1143: 1101: 1108: 1062: 1037: 1018: 1002: 986: 967: 1147: 133:(RM) published in 1970. The overall goal of the RM/T was to define some fundamental 1161: 1135: 1087: 948: 921: 853: 780:
Ordering shows whether the operator > is applicable between values of the domain
744:
E-attribute is any attribute that plays the role of a surrogate (from the E-domain)
130: 548:
is an entity that represents an association between two independent entities; the
257:
can be used to describe entities with attributes. An entity is represented as an
1083: 701:
CATRC (RC-surrogate, R-surrogate, C-surrogate) relates relations and categories
674:
CATRA (RA-surrogate, R-surrogate, A-surrogate) relates relations and attributes
138: 1185: 1174: 1123: 684:
CATAD (AD-surrogate, A-surrogate, D-surrogate) relates attributes and domains
198: 126: 487:) to the writer - namely the primary key of the writer entity. Note that an 461:
The following definition is based on the RM/D model in Date (1983); it does
307:
table implies the corresponding existence of an entity of that type in the
1165: 1091: 953: 936: 926: 909: 858: 841: 233:
that is not an entity and does not have its own identifying surrogate. An
768:
RC-surrogate is the relation-category-label surrogate (from the E-domain)
378:
we can construct the RM/V1 "Employee" relation. This illustrates why the
161:
A later version of RM/T (we shall call it here "RM/D") was described by
1139: 315:"Employee" is a table containing the surrogates of all entities of type 129:
in 1979 and is the name given to a number of extensions to his original
225:
in the modelled universe and is typically identified by a surrogate. A
162: 774:
UserKey shows whether the attribute participates in a user-defined key
471:โ€“ entities that contain a designation. A designative entity is at the 1074: 370:
Note that by performing an OUTER NATURAL JOIN on the RM/T "Employee"
1073:
Grabczewski, E.; Crompton, S.; Robinson, S. K.; Hall, T. H. (2004).
762:
RA-surrogate is the relation-attribute surrogate (from the E-domain)
265:
and its attributes (or immediate properties) are stored in separate
21: 134: 1064:
The Database Relational Model: A Retrospective Review and Analysis
765:
AD-surrogate is the attribute-domain surrogate (from the E-domain)
937:"Extending the database relational model to capture more meaning" 842:"Extending the database relational model to capture more meaning" 303:
for a particular entity type. A surrogate value entered into the
608:
UGI-relation (Unconditional Generalisation by Inclusion) stores
507:
designation whereas an associative entity must contain at least
1072: 1000:
Date, C. J. (1986). "A Practical Approach to Database Design".
759:
C-surrogate is the category label surrogate (from the E-domain)
155: 615:
AGI-relation (Alternative Generalisation by Inclusion) stores
1053:"Thirty Years of Relational: Extending the Relational Model" 747:
E-null is the "entity unknown" surrogate (from the E-domain)
503:
a flight. Hence a designative entity must contain at least
1084:"Database Description with SDM: A Semantic Database Model" 753:
A-surrogate is the attribute surrogate (from the E-domain)
428:โ€“ entities that are neither characteristic or associative. 422:โ€“ superordinate entities that interrelate kernel entities. 771:
RelType is the type of object represented by the relation
750:
R-surrogate is the relation surrogate (from the E-domain)
347:; it plays the role (K-role) of the primary key for that 964:
The Relational Model for Data Base Management: Version 2
910:"A relational model of data for large shared data banks" 741:
E-domain is the domain of all surrogates in the database
756:
D-surrogate is the domain surrogate (from the E-domain)
735:
RN-domain is the domain of all relnames in the database
552:
is an entity in itself because it has a surrogate. A
416:โ€“ subordinate entities that describe kernel entities. 1075:"A Corporate Data Repository for CCLRC using CERIF" 441:โ€“ entities that are not subtypes of another entity. 46:. Unsourced material may be challenged and removed. 1100: 1061: 1001: 720:is the textual name of an attribute. e.g. "Street" 815:RM/T contributed to the body of knowledge called 714:is the textual name of a relation. e.g. "Address" 1183: 1121: 738:PER-domain is the domain of all category labels 137:units, at "atomic" and "molecular" levels, for 872: 726:is the textual name of a domain. e.g. "Salary" 643:UP-relation (Unconditional Precedence) stores 564:surrogate. This lack of a surrogate stops the 190:Introducing some of the new concepts of RM/T: 1155: 622:US-relation (Unconditional Successor) stores 495:a person with a flight, or as an entity that 483:entity because it contains a designation (or 1081: 650:AP-relation (Alternative Precedence) stores 541:Associative Entity and Nonentity Association 253:semantics by describing how the original RM 732:is the category label (from the PER-domain) 629:AS-relation (Alternative Successor) stores 1172: 1012: 594:CG-relation (Characteristic Graph) stores 568:from having, for example, any descriptive 952: 925: 875:Modelling in Data Base Management Systems 857: 277:shares its surrogate with the associated 106:Learn how and when to remove this message 777:VType is the syntactic type of the value 1098: 601:AG-relation (Association Graph) stores 521:These are what we might otherwise call 299:is a relation (table) storing only the 1184: 1034:Relational Database Writings 1991โ€“1994 1015:Relational Database Writings 1989โ€“1991 1004:Relational Database: Selected Writings 636:KG-relation (Cover Membership) stores 152:Australian Computer Science Conference 1152:; a useful survey that includes RM/T. 1059: 1050: 1031: 999: 983:An Introduction to Data Base Systems 980: 961: 941:ACM Transactions on Database Systems 934: 907: 846:ACM Transactions on Database Systems 839: 691:, VType, Ordering) describes domains 587:PG-relation (Property Graph) stores 359:, the other containing the employee 44:adding citations to reliable sources 15: 13: 1122:Peckam, J.; Maryanski, F. (1988). 1013:Date, C. J.; Darwen, Hugh (1992). 894:"Codd's Extended Relational Model" 885: 185: 14: 1203: 891: 645:unconditional succession of event 525:between entities or non-entities. 536:, meaning the entity is unknown. 237:entity has its own surrogate. A 20: 1082:Hammer, M.; McLeod, D. (1981). 681:, UserKey) describes attributes 31:needs additional citations for 866: 833: 671:, RelType) describes relations 1: 826: 806:The Database Relational Model 794: 652:alternative succession of eve 617:generalisation by alternative 343:is that of the corresponding 144: 7: 610:generalisation by inclusion 55:"Relational Model/Tasmania" 10: 1208: 1099:Kroenke, David M. (2001). 386:concepts of RM/T are more 914:Communications of the ACM 901:University College Dublin 119:Relational Model/Tasmania 821:semantic object modeling 577:Directed Graph Relations 214:Entities and Nonentities 1173:Wiederhold, G. (1977). 840:Codd, Edgar F. (1979). 624:unconditional successor 570:characteristic entities 465:appear in Codd (1979): 1124:"Semantic Data Models" 817:semantic data modeling 698:) describes categories 374:and "Employee_Person" 1166:10.1145/500080.500110 1128:ACM Computing Surveys 1092:10.1145/319587.319588 954:10.1145/320107.320109 927:10.1145/362384.362685 859:10.1145/320107.320109 631:alternative successor 566:nonentity association 554:nonentity association 485:designative reference 448:Hence Codd speaks of 1060:Date, C. J. (2001). 1051:Date, C. J. (1999). 1032:Date, C. J. (1995). 981:Date, C. J. (1983). 962:Codd, E. F. (1990). 935:Codd, E. F. (1979). 908:Codd, E. F. (1970). 40:improve this article 1140:10.1145/62061.62062 1107:(Eighth ed.). 1103:Database Processing 694:CATC (C-surrogate, 687:CATD (D-surrogate, 677:CATA (A-surrogate, 667:CATR (R-surrogate, 408:semantic data model 402:The RM/T addresses 399:Molecular Semantics 351:. For example, the 311:. For example, the 249:The RM/T addresses 125:) was published by 558:associative entity 550:associative entity 546:associative entity 267:Property-relations 1175:"Database Design" 556:is similar to an 454:inner associative 394:concept of RM/V1. 295:of an entity. An 116: 115: 108: 90: 1199: 1178: 1169: 1151: 1118: 1106: 1095: 1078: 1069: 1067: 1056: 1047: 1028: 1009: 1007: 996: 977: 958: 956: 931: 929: 904: 898: 879: 878: 877:. North Holland. 870: 864: 863: 861: 837: 654:nt relationships 638:cover membership 335:of an entity. A 333:attribute values 246:Atomic Semantics 131:relational model 111: 104: 100: 97: 91: 89: 48: 24: 16: 1207: 1206: 1202: 1201: 1200: 1198: 1197: 1196: 1182: 1181: 1160:. p. 211. 1115: 1044: 1025: 993: 985:. Vol. 2. 974: 896: 892:Cater, Arthur. 888: 886:Further reading 883: 882: 871: 867: 838: 834: 829: 802:Date and Darwen 797: 560:however it has 259:Entity-relation 188: 186:Summary of RM/T 147: 112: 101: 95: 92: 49: 47: 37: 25: 12: 11: 5: 1205: 1195: 1194: 1180: 1179: 1170: 1153: 1134:(3): 153โ€“189. 1119: 1113: 1096: 1079: 1070: 1057: 1048: 1042: 1029: 1023: 1010: 997: 991: 978: 972: 959: 947:(4): 397โ€“434. 932: 920:(6): 377โ€“387. 905: 887: 884: 881: 880: 865: 852:(4): 397โ€“434. 831: 830: 828: 825: 796: 793: 792: 791: 788: 784: 783: 782: 781: 778: 775: 772: 769: 766: 763: 760: 757: 754: 751: 748: 745: 742: 739: 736: 733: 727: 721: 715: 705: 704: 703: 702: 699: 692: 685: 682: 675: 672: 662: 658: 657: 656: 655: 648: 641: 634: 627: 620: 613: 606: 599: 596:characteristic 592: 582:directed graph 578: 574: 573: 542: 538: 537: 526: 519: 515: 514: 513: 512: 458: 457: 445: 444: 443: 442: 432: 431: 430: 429: 423: 417: 414:Characteristic 400: 396: 395: 367: 366: 365: 364: 329: 323: 322: 321: 320: 309:modelled world 289: 283: 282: 247: 243: 242: 215: 211: 210: 195: 187: 184: 146: 143: 139:data modelling 114: 113: 28: 26: 19: 9: 6: 4: 3: 2: 1204: 1193: 1192:Data modeling 1190: 1189: 1187: 1176: 1171: 1167: 1163: 1159: 1154: 1149: 1145: 1141: 1137: 1133: 1129: 1125: 1120: 1116: 1110: 1105: 1104: 1097: 1093: 1089: 1085: 1080: 1076: 1071: 1066: 1065: 1058: 1054: 1049: 1045: 1039: 1035: 1030: 1026: 1020: 1016: 1011: 1006: 1005: 998: 994: 988: 984: 979: 975: 969: 965: 960: 955: 950: 946: 942: 938: 933: 928: 923: 919: 915: 911: 906: 902: 895: 890: 889: 876: 869: 860: 855: 851: 847: 843: 836: 832: 824: 822: 818: 813: 811: 807: 803: 789: 786: 785: 779: 776: 773: 770: 767: 764: 761: 758: 755: 752: 749: 746: 743: 740: 737: 734: 731: 728: 725: 722: 719: 716: 713: 710: 709: 707: 706: 700: 697: 693: 690: 686: 683: 680: 676: 673: 670: 666: 665: 663: 660: 659: 653: 649: 647:relationships 646: 642: 640:relationships 639: 635: 633:relationships 632: 628: 626:relationships 625: 621: 619:relationships 618: 614: 612:relationships 611: 607: 605:relationships 604: 600: 598:relationships 597: 593: 591:relationships 590: 586: 585: 583: 579: 576: 575: 571: 567: 563: 559: 555: 551: 547: 543: 540: 539: 535: 531: 527: 524: 523:relationships 520: 517: 516: 511:designations. 510: 506: 502: 499:a person and 498: 494: 490: 486: 482: 478: 474: 470: 467: 466: 464: 460: 459: 455: 451: 447: 446: 440: 437: 436: 434: 433: 427: 424: 421: 418: 415: 412: 411: 409: 405: 401: 398: 397: 393: 389: 385: 381: 377: 373: 369: 368: 362: 358: 354: 350: 346: 342: 338: 334: 330: 327: 326: 325: 324: 318: 314: 310: 306: 302: 298: 294: 290: 287: 286: 285: 284: 280: 276: 272: 268: 264: 260: 256: 252: 248: 245: 244: 240: 236: 232: 228: 224: 220: 216: 213: 212: 208: 204: 200: 196: 193: 192: 191: 183: 180: 176: 170: 168: 164: 159: 157: 153: 142: 140: 136: 132: 128: 127:Edgar F. Codd 124: 120: 110: 107: 99: 88: 85: 81: 78: 74: 71: 67: 64: 60: 57: โ€“  56: 52: 51:Find sources: 45: 41: 35: 34: 29:This article 27: 23: 18: 17: 1157: 1131: 1127: 1102: 1063: 1033: 1014: 1003: 982: 963: 944: 940: 917: 913: 874: 868: 849: 845: 835: 814: 810:Date on RM/T 809: 805: 801: 798: 729: 723: 717: 711: 695: 688: 678: 668: 661:RM/T Catalog 651: 644: 637: 630: 623: 616: 609: 602: 595: 588: 581: 569: 565: 561: 557: 553: 549: 545: 533: 529: 522: 518:Associations 508: 504: 500: 496: 492: 488: 484: 480: 476: 472: 468: 462: 453: 450:inner kernel 449: 438: 425: 419: 413: 403: 391: 387: 383: 379: 375: 371: 360: 356: 352: 348: 344: 340: 336: 332: 316: 312: 308: 304: 300: 296: 292: 278: 274: 270: 266: 262: 258: 254: 250: 238: 234: 230: 226: 222: 218: 206: 202: 189: 178: 174: 171: 166: 160: 151: 148: 122: 118: 117: 102: 93: 83: 76: 69: 62: 50: 38:Please help 33:verification 30: 808:(2001) and 603:association 489:associative 481:designative 477:one-to-many 469:Designative 420:Associative 328:P-relations 288:E-relations 271:P-relations 235:independent 179:designative 175:associative 167:designative 96:August 2014 1114:0130648396 1043:0201824590 1024:0201543036 992:0201144743 973:0201141922 827:References 795:RM/T today 528:The value 501:designates 497:designates 493:associates 384:P-relation 380:E-relation 376:P-relation 372:E-relation 357:E-relation 353:P-relation 349:P-relation 345:E-relation 341:P-relation 337:P-relation 331:Store the 313:E-relation 305:E-relation 301:surrogates 297:E-relation 279:P-relation 275:E-relation 263:E-relation 194:Surrogates 163:Chris Date 145:RM history 66:newspapers 787:Operators 475:end of a 456:entities. 404:molecular 390:than the 293:existence 291:Mark the 239:dependent 227:nonentity 207:numerical 199:surrogate 1186:Category 1148:19006625 812:(2003). 589:property 580:Several 392:relation 317:Employee 255:relation 229:is some 221:is some 135:semantic 730:pername 724:domname 718:attname 712:relname 696:pername 689:domname 679:attname 669:relname 273:. Each 80:scholar 1146:  1111:  1040:  1021:  989:  970:  708:where 534:E-null 530:E-null 426:Kernel 388:atomic 361:number 251:atomic 219:entity 156:Hobart 82:  75:  68:  61:  53:  1144:S2CID 897:(PDF) 439:Inner 231:thing 223:thing 203:value 87:JSTOR 73:books 1109:ISBN 1038:ISBN 1019:ISBN 987:ISBN 968:ISBN 819:and 473:many 452:and 382:and 123:RM/T 59:news 1162:doi 1136:doi 1088:doi 949:doi 922:doi 854:doi 544:An 509:two 505:one 463:not 269:or 261:or 217:An 177:or 154:in 42:by 1188:: 1142:. 1132:20 1130:. 1126:. 1086:. 1036:. 1017:. 966:. 943:. 939:. 918:13 916:. 912:. 899:. 848:. 844:. 562:no 281:s. 197:A 1177:. 1168:. 1164:: 1150:. 1138:: 1117:. 1094:. 1090:: 1077:. 1068:. 1055:. 1046:. 1027:. 1008:. 995:. 976:. 957:. 951:: 945:4 930:. 924:: 903:. 862:. 856:: 850:4 572:. 363:. 319:. 121:( 109:) 103:( 98:) 94:( 84:ยท 77:ยท 70:ยท 63:ยท 36:.

Index


verification
improve this article
adding citations to reliable sources
"Relational Model/Tasmania"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
Edgar F. Codd
relational model
semantic
data modelling
Hobart
Chris Date
surrogate
semantic data model
semantic data modeling
semantic object modeling
"Extending the database relational model to capture more meaning"
doi
10.1145/320107.320109
"Codd's Extended Relational Model"
University College Dublin
"A relational model of data for large shared data banks"
doi
10.1145/362384.362685
"Extending the database relational model to capture more meaning"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

โ†‘