Download name varchar

Chapter 9: Object-Based Databases
Database System Concepts, 5th Ed.
©Sang Ho Lee
http://dblab.ssu.ac.kr
Chapter 9: Object-Based Databases
 Complex Data Types and Object Orientation
 Structured Data Types and Inheritance in SQL
 Table Inheritance
 Array and Multiset Types in SQL
 Object Identity and Reference Types in SQL
 Implementing O-R Features
 Persistent Programming Languages
 Comparison of Object-Oriented and Object-Relational Databases
Database System Concepts - 5th Edition
9.2
©Sang Ho Lee
Historically speaking….
 1980’s: Relational data model and systems prevail
 Late 80’s: Object-oriented data model emerges
 Early 90’s: Early versions of object-oriented database systems appear
in the market
 Mid 90’s: Attempts to accommodate object-oriented data model into
relational data model
(object-relational data model)
 00’s:

Venders started to ship “object-relational” database systems

Standard SQL, SQL3, is finalized
Database System Concepts - 5th Edition
9.3
©Sang Ho Lee
Object-Relational Data Models
 Extend the relational data model by including object orientation and
constructs to deal with added data types.
 Allow attributes of tuples to have complex types, including non-atomic
values such as nested relations.
 Preserve relational foundations, in particular the declarative access to
data, while extending modeling power.
 Upward compatibility with existing relational languages.
Database System Concepts - 5th Edition
9.4
©Sang Ho Lee
OO vs. ER
 Modeling primitives in ER

Entity (entity set)

Relationship (relationship set)

Properties

Attribute
 Modeling primitives in OO

Object (class)

Properties

Attribute

Relationship

Method
Database System Concepts - 5th Edition
9.5
©Sang Ho Lee
Complex Data Types
 Motivation:

Permit non-atomic domains (atomic  indivisible)

Example of non-atomic domain: set of integers or set of tuples

Allows more intuitive modeling for applications with complex data
 Intuitive definition:

allow relations whenever we allow atomic (scalar) values —
relations within relations

Retains mathematical foundation of relational model

Violates first normal form.
Database System Concepts - 5th Edition
9.6
©Sang Ho Lee
Example of a Nested Relation
 Example: library information system
 Each book has

title,

a set of authors,

publisher, and

a set of keywords
 Non-1NF relation, books
Database System Concepts - 5th Edition
9.7
©Sang Ho Lee
1NF Version of Nested Relation
1NF version of books, flat-books
flat-books
Database System Concepts - 5th Edition
9.8
©Sang Ho Lee
4NF Decomposition of Nested Relation
 Remove awkwardness of flat-books by assuming that the following
multivalued dependencies hold:

title
author

title
keyword

title
pub-name, pub-branch
 Decompose flat-books into 4NF using the schemas:

(title, author )

(title, keyword )

(title, pub-name, pub-branch )
Database System Concepts - 5th Edition
9.9
©Sang Ho Lee
4NF Decomposition of flat–books
Database System Concepts - 5th Edition
9.10
©Sang Ho Lee
Problems with 4NF Schema
 4NF design requires users to include joins in their queries.
 1NF relational view flat-books defined by join of 4NF relations:

eliminates the need for users to perform joins,

but loses the one-to-one correspondence between tuples and
documents.

has a large amount of redundancy
 Nested relations representation is much more natural here.
Database System Concepts - 5th Edition
9.11
©Sang Ho Lee
Complex Types and SQL:1999
 Extensions to SQL to support complex types include:

Collection and large object types
 Nested relations are an example of collection types
 Structured types
 Nested record structures like composite attributes

Inheritance
 Object orientation
 Including object identifiers and references
 Our description is mainly based on the SQL:1999 standard
 Not fully implemented in any database system currently

But some features are present in each of the major commercial
database systems
 Read the manual of your database system to see what it
supports
Database System Concepts - 5th Edition
9.12
©Sang Ho Lee
Structured Types and Inheritance in SQL

Structured types can be declared and used in SQL
create type Name as
(firstname
varchar(20),
lastname
varchar(20))
final
create type Address as
(street
varchar(20),
city
varchar(20),
zipcode
varchar(20))
not final



Note: final and not final indicate whether subtypes can be created
Structured types can be used to create tables with composite attributes
create table customer (
name
Name,
address Address,
dateOfBirth date)
Dot notation used to reference components: name.firstname
Database System Concepts - 5th Edition
9.13
©Sang Ho Lee
Structured Types (cont.)
 User-defined row types
create type CustomerType as (
name Name,
address Address,
dateOfBirth date)
not final
 Can then create a table whose rows are a user-defined type
create table customer of CustomerType
Database System Concepts - 5th Edition
9.14
©Sang Ho Lee
Methods

Can add a method declaration with a structured type.
method ageOnDate (onDate date)
returns interval year

Method body is given separately.
create instance method ageOnDate (onDate date)
returns interval year
for CustomerType
// note, type name (not relation name)
begin
return onDate - self.dateOfBirth;
// “self” refers to the Customer instance on which the method is invoked
end

We can now find the age of each customer:
select name.lastname, ageOnDate (current_date)
from customer
Database System Concepts - 5th Edition
9.15
©Sang Ho Lee
Structured Types
 Structured types allow composite attributes of E-R diagrams to be
represented directly.
 Unnamed row types can also be used in SQL:1999 to define
composite attributes

E.g. we can omit the declaration of type Publisher and instead use
the following in declaring the type Book
publisher row (name varchar(20),
branch varchar(20))
 Similarly, collection types allow multivalued attributes of E-R diagrams
to be represented directly.
Database System Concepts - 5th Edition
9.16
©Sang Ho Lee
Structured Types (Cont.)

We can create tables without creating an intermediate type

For example, the table books could also be defined as follows:
create table books
(title varchar(20),
author-array varchar(20) array[10],
pub-date date,
publisher Publisher
keyword-list setof(varchar(20)))

Methods can be part of the type definition of a structured type:
create type Employee as (
name varchar(20),
salary integer)
method giveraise (percent integer)

We create the method body separately
create method giveraise (percent integer) for Employee
begin
set self.salary = self.salary + (self.salary * percent) / 100;
end
Database System Concepts - 5th Edition
9.17
©Sang Ho Lee
Creation of Values of Complex Types

Values of structured types are created using constructor functions
E.g. Publisher(‘McGraw-Hill’, ‘New York’)
 Note: a value is not an object


SQL:1999 constructor functions

E.g.
create function Publisher (n varchar(20), b varchar(20))
returns Publisher
begin
set name=n;
/* set self.name = n; */
set branch=b;
/* set self.branch = b; */
end
 Every structured type has a default constructor with no arguments,
others can be defined as required

Values of row type can be constructed by listing values in parantheses

E.g. given row type row (name varchar(20),
branch varchar(20))

We can assign (`McGraw-Hill’,`New York’) as a value of above type
Database System Concepts - 5th Edition
9.18
©Sang Ho Lee
Type Inheritance
 Reusability !!!
 Suppose that we have the following type definition for people:
create type Person
(name varchar(20),
address varchar(20))
 Using inheritance to define the student and teacher types
create type Student
under Person
(degree
varchar(20),
department varchar(20))
create type Teacher
under Person
(salary
integer,
department varchar(20))
 Subtypes can redefine methods by using overriding method in place
of method in the method declaration
Database System Concepts - 5th Edition
9.19
©Sang Ho Lee
Multiple Inheritance
 SQL:1999 and SQL:2003 do not support multiple inheritance
 If our type system supports multiple inheritance, we can define a type
for teaching assistant as follows:
create type Teaching Assistant
under Student, Teacher
 To avoid a conflict between the two occurrences of department we
can rename them
create type Teaching Assistant
under
Student with (department as student_dept ),
Teacher with (department as teacher_dept )
Database System Concepts - 5th Edition
9.20
©Sang Ho Lee
Table Inheritance
 Table inheritance allows an object to have multiple types by allowing
an entity to exist in more than one table at once.
 E.g. people table: create table people of Person
 We can then define the students and teachers tables as subtables of
people
create table students of Student
under people
create table teachers of Teacher
under people
 Each tuple in a subtable (e.g. students and teachers) is implicitly
present in its supertables (e.g. people)
 If a query uses the table “people”, it will return tuples in “people”,
“students” and “teachers” (only those attributes that present in
people can be accessed)
 SQL:1999 provides a keyworld “only” (for example, “only people”)
to search the table only
Database System Concepts - 5th Edition
9.21
©Sang Ho Lee
Consistency Requirements for Subtables
 Consistency requirements on subtables and supertables.

Each tuple of the supertable (e.g. people) can correspond to at
most one tuple in each of the subtables (e.g. students and
teachers)

Additional constraint in SQL:1999:
All tuples corresponding to each other (that is, with the same
values for inherited attributes) must be derived from one tuple
(inserted into one table).

That is, each entity must have a most specific type

We cannot have a tuple in people corresponding to a tuple
each in students and teachers
Database System Concepts - 5th Edition
9.22
©Sang Ho Lee
Array and Multiset Types in SQL

Example of array and multiset declaration:
create type Publisher as
(name
varchar(20),
branch
varchar(20))
create type Book as
(title
varchar(20),
author-array varchar(20) array [10],
pub-date
date,
publisher
Publisher,
keyword-set varchar(20) multiset )
create table books of Book

Similar to the nested relation books, but with array of authors
instead of set
Database System Concepts - 5th Edition
9.23
©Sang Ho Lee
Creation of Collection Values
 Array construction
array [‘Silberschatz’,`Korth’,`Sudarshan’]
 Multisets

multiset [‘computer’, ‘database’, ‘SQL’]
 To create a tuple of the type defined by the books relation:
(‘Compilers’, array[`Smith’,`Jones’],
Publisher (`McGraw-Hill’,`New York’),
multiset [`parsing’,`analysis’ ])
 To insert the preceding tuple into the relation books
insert into books
values
(‘Compilers’, array[`Smith’,`Jones’],
Publisher (`McGraw-Hill’,`New York’),
multiset [`parsing’,`analysis’ ])
Database System Concepts - 5th Edition
9.24
©Sang Ho Lee
Querying Collection-Valued Attributes

To find all books that have the word “database” as a keyword,
select title
from books
where ‘database’ in (unnest(keyword-set ))


Collection-valued attributes can be treated much like relations using the
keyword “unnest”
We can access individual elements of an array by using indices

E.g.: If we know that a particular book has three authors, we could write:
select author-array[1], author-array[2], author-array[3]
from books
where title = `Database System Concepts’


To get a relation containing pairs of the form “title, author-name” for each book
and each author of the book
select B.title, A.author
from books as B, unnest (B.author-array) as A (author )
To retain ordering information we add a with ordinality clause
select B.title, A.author, A.position
from books as B, unnest (B.author-array) with ordinality as
A (author, position )
Database System Concepts - 5th Edition
9.25
©Sang Ho Lee
Unnesting
 The transformation of a nested relation into a form with fewer
(or no) relation-valued attributes is called unnesting.
 E.g.
select title, A.author, publisher.name as pub_name,
publisher.branch as pub_branch, K.keyword
from books as B, unnest(B.author_array ) as A(author ),
unnest(B.keyword_set ) as K(keyword )
See the flat-books table
Database System Concepts - 5th Edition
9.26
©Sang Ho Lee
Nesting

Nesting is the opposite of unnesting, creating a collection-valued attribute

NOTE: SQL:1999 does not support nesting

Nesting can be done in a manner similar to aggregation, but using the function
collect() in place of an aggregation operation, to create a multiset

To nest the flat-books relation on the attribute keyword:

select title, author, Publisher (pub_name, pub_branch ) as publisher,
collect (keyword) as keyword_set
from flat-books
group by title, author, publisher // See fig 9.4 in the textbook
To nest on both authors and keywords:
select title, collect (author ) as author_set,
Publisher (pub_name, pub_branch) as publisher,
collect (keyword ) as keyword_set
from flat-books
group by title, publisher
Database System Concepts - 5th Edition
9.27
©Sang Ho Lee
A Partially Nested Version of the flat-books Relation
 To nest the flat-books relation on the attribute keyword (fig. 9.4 of
textbook)
Database System Concepts - 5th Edition
9.28
©Sang Ho Lee
1NF Version of Nested Relation
1NF version of books
flat-books
Database System Concepts - 5th Edition
9.29
©Sang Ho Lee
Nesting (Cont.)
 Another approach to creating nested relations is to use subqueries in
the select clause.
select title,
array ( select author
from authors as A
where A.title = B.title
order by A.author) as author_array,
Publisher (pub-name, pub-branch) as publisher,
multiset (select keyword
from keywords as K
where K.title = B.title) as keyword_set
from books4 as B
Database System Concepts - 5th Edition
9.30
©Sang Ho Lee
Reference Types
 Object-oriented languages provide the ability to create and refer to
objects.
 In SQL:1999

References are to tuples, and

References must be scoped,

I.e., can only point to tuples in one specified table
Database System Concepts - 5th Edition
9.31
©Sang Ho Lee
Object-Identity and Reference Types
 Define a type Department with a field name and a field head which is a
reference to the type Person, with table people as scope:
create type Department (
name varchar (20),
head ref (Person) scope people)
// Person: type name
// people: table name
 We can then create a table departments as follows
create table departments of Department
 We can omit the declaration scope people from the type declaration
and instead make an addition to the create table statement:
create table departments of Department
(head with options scope people)
Database System Concepts - 5th Edition
9.32
©Sang Ho Lee
System Generated Identifiers
 SQL:1999 requires a special attribute (called self-referential attribute)
to be declared to store the object identifier

SQL:1999 does not support the ref() function of Oracle
 The self-referential attributes can be generated either by the system or
the user
 The self-referential attribute is declared by adding a ref is clause to
the “create table” statement:
create table people of Person
ref is person_id system generated
 Here, person_id is an attribute name, not a keyword.
Database System Concepts - 5th Edition
9.33
©Sang Ho Lee
Initializing Reference-Typed Values
 To create a tuple with a reference value, we can first create the tuple
with a null reference and then set the reference separately:
insert into departments
values (`CS’, null)
update departments
set head = (select p.person_id // ref(p) in Oracle
from people as p
where name = `John’)
where name = `CS’
departments(name, head)
people(person_id, name, address)
John
CS
Database System Concepts - 5th Edition
9.34
©Sang Ho Lee
User Generated Identifiers
 The type of the object-identifier must be specified as part of the type
definition of the referenced table, and
 The table definition must specify that the reference is user generated
create type Person
(name varchar(20)
address varchar(20))
ref using varchar(20)
create table people of Person
ref is person_id user generated
 When creating a tuple, we must provide a unique value for the identifier:
insert into people (person_id, name, address ) values
(‘01284567’, ‘John’, `23 Coyote Run’)
 We can then use the identifier value when inserting a tuple into
departments
 Avoids need for a separate query to retrieve the identifier:
insert into departments
values(`CS’, `02184567’)
Database System Concepts - 5th Edition
9.35
©Sang Ho Lee
User Generated Identifiers (Cont.)
 Can use an existing primary key value as the identifier:
create type Person
(name varchar (20) primary key,
address varchar(20))
ref from (name)
create table people of Person
ref is person_id derived
 When inserting a tuple for departments, we can then use
insert into departments
values(`CS’,`John’)
Database System Concepts - 5th Edition
9.36
©Sang Ho Lee
Path Expressions
 Find the names and addresses of the heads of all departments:
select head –>name, head –>address
from departments
 An expression such as “head–>name” is called a path expression
 Path expressions help avoid explicit joins

If department head were not a reference, a join of departments
with people would be required to get at the address

Makes expressing the query much easier for the user
Database System Concepts - 5th Edition
9.37
©Sang Ho Lee
Implementing O-R Features
 Similar to how E-R features are mapped onto relation schemas
 Subtable implementation

Each table stores primary key and those attributes defined in that
table
or,

Each table stores both locally defined and inherited attributes
Database System Concepts - 5th Edition
9.38
©Sang Ho Lee
Object-Oriented Languages
 Object-oriented concepts can be used in different ways

Object-orientation can be used as a design tool, and be encoded
into, for example, a relational database


analogous to modeling data with E-R diagram and then
converting to a set of relations)
The concepts of object orientation can be incorporated into a
programming language that is used to manipulate the database.

Object-relational systems – add complex types and objectorientation to relational language.

Persistent programming languages – extend object-oriented
programming language to deal with databases by adding
concepts such as persistence and collections.
Database System Concepts - 5th Edition
9.39
©Sang Ho Lee
Persistent Programming Languages
 Persistent Programming languages allow objects to be created and
stored in a database, and used directly from a programming language
 allow data to be manipulated directly from the programming
language
No need to go through SQL.
 No need for explicit format (type) changes
 format changes are carried out transparently by system
 Without a persistent programming language, format changes
becomes a burden on the programmer

– More code to be written
– More chance of bugs
 allow objects to be manipulated in-memory
 no need to explicitly load from or store to the database
– Saved code, and saved overhead of loading/storing large
amounts of data
Database System Concepts - 5th Edition
9.40
©Sang Ho Lee
Persistent Prog. Languages (Cont.)
 Drawbacks of persistent programming languages

Due to power of most programming languages, it is easy to make
programming errors that damage the database.

Complexity of languages makes automatic high-level optimization
more difficult.

Do not support declarative querying as well as relational
databases
Database System Concepts - 5th Edition
9.41
©Sang Ho Lee
Persistence of Objects
 Approaches to make transient objects persistent include establishing

Persistence by Class – declare all objects of a class to be
persistent; simple but inflexible.

Persistence by Creation – extend the syntax for creating objects to
specify that that an object is persistent.

Persistence by Marking – an object that is to persist beyond
program execution is marked as persistent before program
termination.

Persistence by Reachability - declare (root) persistent objects;
objects are persistent if they are referred to (directly or indirectly)
from a root object.

Easier for programmer, but more overhead for database
system
Database System Concepts - 5th Edition
9.42
©Sang Ho Lee
Object Identity and Pointers
 Degrees of permanence of object identity

Intraprocedure: only during execution of a single procedure


Intraprogram: only during execution of a single program or query


Example: global variables in programming languages
Interprogram: across program executions, but not if data-storage
format on disk changes


Example: local variables within procedures
Example: pointers to file-system data on disk
Persistent: interprogram, plus persistent across data
reorganizations
Database System Concepts - 5th Edition
9.43
©Sang Ho Lee
Object Identity and Pointers (cont.)
 Persistent versions of C++ and Java have been implemented


C++

ODMG C++

ObjectStore, Versant
Java

Java Database Objects (JDO)
Database System Concepts - 5th Edition
9.44
©Sang Ho Lee
Object Identity and Pointers (Cont.)
 In O-O languages such as C++, an object identifier is actually an in-
memory pointer.
 Persistent pointer – persists beyond program execution

can be thought of as a pointer into the database


E.g. specify file identifier and offset into the file
Problems due to database reorganization have to be dealt with by
keeping forwarding pointers
Database System Concepts - 5th Edition
9.45
©Sang Ho Lee
Comparison of O-O and O-R Databases
 Relational systems

simple data types, powerful query languages, high protection.
 Persistent-programming-language-based OODBs

complex data types, integration with programming language, high
performance.
 Object-relational systems

complex data types, powerful query languages, high protection.
 Note: Many real systems blur these boundaries

E.g. persistent programming language built as a wrapper on a
relational database offers first two benefits, but may have poor
performance.
Database System Concepts - 5th Edition
9.46
©Sang Ho Lee
End of Chapter
Database System Concepts, 5th Ed.
©Sang Ho Lee
http://dblab.ssu.ac.kr