1. Trang chủ
  2. » Công Nghệ Thông Tin

slide cơ sở dữ liệu tiếng anh chương (28) object-relational dbmsstransparencies

108 347 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Cấu trúc

  • Chapter 28

  • Chapter 28 - Objectives

  • Market Share

  • ORDBMSs

  • ORDBMSs - Features

  • Slide 6

  • Stonebraker’s View

  • Advantages of ORDBMSs

  • Disadvantages of ORDBMSs

  • CADF Manifesto

  • Slide 11

  • Slide 12

  • Slide 13

  • Third Manifesto

  • Slide 15

  • Postgres

  • Slide 17

  • SQL:2003 - New OO Features

  • Row Types

  • Example 28.1 - Use of Row Type

  • User-Defined Types (UDTs)

  • Slide 22

  • UDTs – Encapsulation and get/set functions

  • UDTs – Constructors and NEW expression

  • UDTs - Example Constructor Method

  • Example 28.2 - Definition of new UDT

  • Slide 27

  • Subtypes and Supertypes

  • Example 28.3 - Creation of Subtype

  • Slide 30

  • User-Defined Routines (UDRs)

  • Slide 32

  • Slide 33

  • Slide 34

  • Slide 35

  • Polymorphism

  • Reference Types and Object Identity

  • Slide 38

  • Example 28.4 - Table Creation based on UDT

  • Example 28.5 - Using Reference Type to Define a Relationship

  • Subtables and Supertables

  • Example 28.6 - Creation of Subtable

  • Example 28.7 - Retrieve Specific Column/Rows

  • Example 28.8 - Invoke User-Defined Function

  • Example 28.9 - Use of ONLY

  • Slide 46

  • Example 28.10 - Use of Dereference Operator

  • Slide 48

  • Collection Types

  • Collection Types

  • Example 28.11 - Use of ARRAY Collection

  • MULTISET

  • Operations on MULTISET

  • Slide 54

  • Aggregate Functions for MULTISET

  • Predicates for use with MULTISET

  • Example 28.12 - Use of Collection MULTISET

  • Example 28.13 – FUSION and INTERSECTION

  • Slide 59

  • Example 28.14 – Typed Views

  • Persistent Stored Modules (SQL/PSM)

  • Persistent Stored Modules (SQL/PSM)

  • SQL/PSM - Condition Handling

  • Triggers

  • Slide 65

  • Slide 66

  • Slide 67

  • Example 28.14 - Use of AFTER Trigger

  • Example 28.15 - Use of AFTER Trigger with Condition

  • Triggers - Advantages and Disadvantages

  • Large Objects

  • Example 28.16 - Use of CLOB and BLOB

  • Recursion

  • Recursion

  • Slide 75

  • Query Processing and Optimization

  • Example 28.18 - Use of UDFs Revisited

  • Slide 78

  • Query Processing and Optimization

  • Example 28.19 - Different QP Heuristics

  • Slide 81

  • Slide 82

  • Slide 83

  • New Index Types

  • Slide 85

  • Slide 86

  • Object-Oriented Extensions in Oracle

  • Object Types in Oracle

  • Slide 89

  • Slide 90

  • Slide 91

  • Methods in Oracle

  • Slide 93

  • Slide 94

  • Object Identifiers

  • REF Data Type

  • Slide 97

  • Slide 98

  • Nested Tables

  • Slide 100

  • Slide 101

  • Manipulating Object Tables

  • Slide 103

  • Querying Object Tables

  • Object Views

  • Data Modeling Comparison of ORDBMS and OODBMS

  • Data Access Comparison of ORDBMS and OODBMS

  • Data Sharing Comparison of ORDBMS and OODBMS

Nội dung

1 Chapter 28 Object-Relational DBMSs Transparencies © Pearson Education Limited 1995, 2005 2 Chapter 28 - Objectives ◆ How relational model has been extended to support advanced database applications. ◆ Features proposed in third-generation database system manifestos from CADF and Darwen/Date. ◆ Extensions to relational data model in Postgres. ◆ Object-oriented features in SQL:2003. ◆ Extensions to QP to support advanced queries. ◆ Object-oriented extensions to Oracle. ◆ How OODBMSs and ORDBMSs compare in terms of data modeling, data access, and data sharing. © Pearson Education Limited 1995, 2005 3 Market Share ◆ RDBMSs currently dominant database technology with estimated sales $6 - $10 billion per year ($25 billion with tools sales included). ◆ OODBMS market still small, but still finds new applications areas such as Web. ◆ Some analysts expect OODBMS market to grow at a faster rate than total database market, but unlikely to overtake relational systems. © Pearson Education Limited 1995, 2005 4 ORDBMSs ◆ Vendors of RDBMSs conscious of threat and promise of OODBMS. ◆ Agree that RDBMSs not currently suited to advanced database applications, and added functionality is required. ◆ Reject claim that extended RDBMSs will not provide sufficient functionality or will be too slow to cope adequately with new complexity. ◆ Can remedy shortcomings of relational model by extending model with OO features. © Pearson Education Limited 1995, 2005 5 ORDBMSs - Features ◆ OO features being added include: – user-extensible types, – encapsulation, – inheritance, – polymorphism, – dynamic binding of methods, – complex objects including non-1NF objects, – object identity. © Pearson Education Limited 1995, 2005 6 ORDBMSs - Features ◆ However, no single extended relational model. ◆ All models: – share basic relational tables and query language, – all have some concept of ‘object’, – some can store methods (or procedures or triggers). ◆ Some analysts predict ORDBMS will have 50% larger share of market than RDBMS. © Pearson Education Limited 1995, 2005 7 Stonebraker’s View © Pearson Education Limited 1995, 2005 8 Advantages of ORDBMSs ◆ Resolves many of known weaknesses of RDBMS. ◆ Reuse and sharing: – reuse comes from ability to extend server to perform standard functionality centrally; – gives rise to increased productivity both for developer and end-user. ◆ Preserves significant body of knowledge and experience gone into developing relational applications. © Pearson Education Limited 1995, 2005 9 Disadvantages of ORDBMSs ◆ Complexity. ◆ Increased costs. ◆ Proponents of relational approach believe simplicity and purity of relational model are lost. ◆ Some believe RDBMS is being extended for what will be a minority of applications. ◆ OO purists not attracted by extensions either. ◆ SQL now extremely complex. © Pearson Education Limited 1995, 2005 10 CADF Manifesto ◆ A 3rd generation DBMS must have a rich type system. ◆ Inheritance is a good idea. ◆ Functions, including database procedures and methods and encapsulation are a good idea. ◆ Unique identifiers for records should be assigned by the DBMS only if a user-defined primary key is not available. © Pearson Education Limited 1995, 2005 . 1 Chapter 28 Object-Relational DBMSs Transparencies © Pearson Education Limited 1995, 2005 2 Chapter 28 - Objectives ◆ How

Ngày đăng: 22/10/2014, 10:19

TỪ KHÓA LIÊN QUAN

TÀI LIỆU CÙNG NGƯỜI DÙNG

TÀI LIỆU LIÊN QUAN