Advanced Data Types
Advanced Data Types
Applications
Temporal Data
Spatial and Geographic Databases
Multimedia Databases
Mobility and Personal Databases
Database System Concepts - 6th Edition 25.2 ©Silberschatz, Korth and Sudarshan
Time In Databases
While most databases tend to model reality at a point in time (at the
“current” time), temporal databases model the states of the real world
across time.
Facts in temporal relations have associated times when they are valid,
which can be represented as a union of intervals.
The transaction time for a fact is the time interval during which the fact
is current within the database system.
In a temporal relation, each tuple has an associated time when it is true;
the time may be either valid time or transaction time.
A bi-temporal relation stores both valid and transaction time.
Database System Concepts - 6th Edition 25.3 ©Silberschatz, Korth and Sudarshan
Time In Databases (Cont.)
Example of a temporal relation:
Database System Concepts - 6th Edition 25.4 ©Silberschatz, Korth and Sudarshan
Time Specification in SQL-92
date: four digits for the year (1--9999), two digits for the month (1--12),
and two digits for the date (1--31).
time: two digits for the hour, two digits for the minute, and two digits for
the second, plus optional fractional digits.
timestamp: the fields of date and time, with six fractional digits for the
seconds field.
Times are specified in the Universal Coordinated Time, abbreviated
UTC (from the French); supports time with time zone.
interval: refers to a period of time (e.g., 2 days and 5 hours), without
specifying a particular time when this period starts; could more
accurately be termed a span.
Database System Concepts - 6th Edition 25.5 ©Silberschatz, Korth and Sudarshan
Temporal Query Languages
Predicates precedes, overlaps, and contains on time intervals.
Intersect can be applied on two intervals, to give a single (possibly
empty) interval; the union of two intervals may or may not be a single
interval.
A snapshot of a temporal relation at time t consists of the tuples that
are valid at time t, with the time-interval attributes projected out.
Temporal selection: involves time attributes
Temporal projection: the tuples in the projection inherit their time-
intervals from the tuples in the original relation.
Temporal join: the time-interval of a tuple in the result is the
intersection of the time-intervals of the tuples from which it is derived. It
intersection is empty, tuple is discarded from join.
Database System Concepts - 6th Edition 25.6 ©Silberschatz, Korth and Sudarshan
Temporal Query Languages (Cont.)
Functional dependencies must be used with care: adding a time field
may invalidate functional dependency
τ
A temporal functional dependency x → Y holds on a relation
schema R if, for all legal instances r of R, all snapshots of r satisfy the
functional dependency X →Y.
SQL:1999 Part 7 (SQL/Temporal) is a proposed extension to
SQL:1999 to improve support of temporal data.
Database System Concepts - 6th Edition 25.7 ©Silberschatz, Korth and Sudarshan
Spatial and Geographic Databases
Database System Concepts - 6th Edition 25.9 ©Silberschatz, Korth and Sudarshan
Represented of Geometric Information
Database System Concepts - 6th Edition 25.10 ©Silberschatz, Korth and Sudarshan
Representation of Geometric Constructs
Database System Concepts - 6th Edition 25.11 ©Silberschatz, Korth and Sudarshan
Representation of Geometric Information (Cont.)
Database System Concepts - 6th Edition 25.12 ©Silberschatz, Korth and Sudarshan
Design Databases
Represent design components as objects (generally geometric
objects); the connections between the objects indicate how the
design is structured.
Simple two-dimensional objects: points, lines, triangles, rectangles,
polygons.
Complex two-dimensional objects: formed from simple objects via
union, intersection, and difference operations.
Complex three-dimensional objects: formed from simpler objects
such as spheres, cylinders, and cuboids, by union, intersection,
and difference operations.
Wireframe models represent three-dimensional surfaces as a set of
simpler objects.
Database System Concepts - 6th Edition 25.13 ©Silberschatz, Korth and Sudarshan
Representation of Geometric Constructs
Database System Concepts - 6th Edition 25.14 ©Silberschatz, Korth and Sudarshan
Geographic Data
Database System Concepts - 6th Edition 25.15 ©Silberschatz, Korth and Sudarshan
Geographic Data (Cont.)
Vector data are constructed from basic geometric objects: points, line
segments, triangles, and other polygons in two dimensions, and
cylinders, spheres, cuboids, and other polyhedrons in three
dimensions.
Vector format often used to represent map data.
z Roads can be considered as two-dimensional and represented by
lines and curves.
z Some features, such as rivers, may be represented either as
complex curves or as complex polygons, depending on whether
their width is relevant.
z Features such as regions and lakes can be depicted as polygons.
Database System Concepts - 6th Edition 25.16 ©Silberschatz, Korth and Sudarshan
Applications of Geographic Data
Examples of geographic data
z map data for vehicle navigation
z distribution network information for power, telephones, water
supply, and sewage
Vehicle navigation systems store information about roads and
services for the use of drivers:
z Spatial data: e.g., road/restaurant/gas-station coordinates
z Non-spatial data: e.g., one-way streets, speed limits, traffic
congestion
Global Positioning System (GPS) unit - utilizes information
broadcast from GPS satellites to find the current location of user with
an accuracy of tens of meters.
z increasingly used in vehicle navigation systems as well as utility
maintenance applications.
Database System Concepts - 6th Edition 25.17 ©Silberschatz, Korth and Sudarshan
Spatial Queries
Nearness queries request objects that lie near a specified location.
Nearest neighbor queries, given a point or an object, find the
nearest object that satisfies given conditions.
Region queries deal with spatial regions. e.g., ask for objects that
lie partially or fully inside a specified region.
Queries that compute intersections or unions of regions.
Spatial join of two spatial relations with the location playing the role
of join attribute.
Database System Concepts - 6th Edition 25.18 ©Silberschatz, Korth and Sudarshan
Spatial Queries (Cont.)
Spatial data is typically queried using a graphical query language;
results are also displayed in a graphical manner.
Graphical interface constitutes the front-end
Extensions of SQL with abstract data types, such as lines,
polygons and bit maps, have been proposed to interface with back-
end.
z allows relational databases to store and retrieve spatial
information
z Queries can use spatial conditions (e.g., contains or overlaps).
z queries can mix spatial and nonspatial conditions
Database System Concepts - 6th Edition 25.19 ©Silberschatz, Korth and Sudarshan
Indexing of Spatial Data
Database System Concepts - 6th Edition 25.20 ©Silberschatz, Korth and Sudarshan
Division of Space by a k-d Tree
Each line in the figure (other than the outside box) corresponds to a
node in the k-d tree.
z The maximum number of points in a leaf node has been set to 1.
The numbering of the lines in the figure indicates the level of the tree
at which the corresponding node appears.
Database System Concepts - 6th Edition 25.21 ©Silberschatz, Korth and Sudarshan
Division of Space by Quadtrees
Quadtrees
Each node of a quadtree is associated with a rectangular region of space;
the top node is associated with the entire target space.
Each non-leaf nodes divides its region into four equal sized quadrants
z Correspondingly each such node has four child nodes corresponding to
the four quadrants and so on
Leaf nodes have between zero and some fixed maximum number of points
(set to 1 in example).
Database System Concepts - 6th Edition 25.22 ©Silberschatz, Korth and Sudarshan
Quadtrees (Cont.)
PR quadtree: stores points; space is divided based on regions, rather
than on the actual set of points stored.
Region quadtrees store array (raster) information.
z A node is a leaf node is all the array values in the region that it
covers are the same. Otherwise, it is subdivided further into four
children of equal area, and is therefore an internal node.
z Each node corresponds to a sub-array of values.
z The sub-arrays corresponding to leaves either contain just a single
array element, or have multiple array elements, all of which have
the same value.
Extensions of k-d trees and PR quadtrees have been proposed to
index line segments and polygons
z Require splitting segments/polygons into pieces at partitioning
boundaries
Same segment/polygon may be represented at several leaf
nodes
Database System Concepts - 6th Edition 25.23 ©Silberschatz, Korth and Sudarshan
R-Trees
Database System Concepts - 6th Edition 25.24 ©Silberschatz, Korth and Sudarshan
R Trees (Cont.)
A rectangular bounding box is associated with each tree node.
z Bounding box of a leaf node is a minimum sized rectangle that
contains all the rectangles/polygons associated with the leaf node.
z The bounding box associated with a non-leaf node contains the
bounding box associated with all its children.
z Bounding box of a node serves as its key in its parent node (if any)
z Bounding boxes of children of a node are allowed to overlap
A polygon is stored only in one node, and the bounding box of the
node must contain the polygon.
z The storage efficiency or R-trees is better than that of k-d trees or
quadtrees since a polygon is stored only once.
Database System Concepts - 6th Edition 25.25 ©Silberschatz, Korth and Sudarshan
Example R-Tree
A set of rectangles (solid line) and the bounding boxes (dashed line) of the
nodes of an R-tree for the rectangles. The R-tree is shown on the right.
Database System Concepts - 6th Edition 25.26 ©Silberschatz, Korth and Sudarshan
Search in R-Trees
To find data items (rectangles/polygons) intersecting (overlaps) a
given query point/region, do the following, starting from the root node:
z If the node is a leaf node, output the data items whose keys
intersect the given query point/region.
z Else, for each child of the current node whose bounding box
overlaps the query point/region, recursively search the child
Can be very inefficient in worst case since multiple paths may need to
be searched
z but works acceptably in practice.
Simple extensions of search procedure to handle predicates
contained-in and contains
Database System Concepts - 6th Edition 25.27 ©Silberschatz, Korth and Sudarshan
Insertion in R-Trees
To insert a data item:
z Find a leaf to store it, and add it to the leaf
To find leaf, follow a child (if any) whose bounding box contains
bounding box of data item, else child whose overlap with data
item bounding box is maximum
z Handle overflows by splits (as in B+-trees)
Split procedure is different though (see below)
z Adjust bounding boxes starting from the leaf upwards
Split procedure:
z Goal: divide entries of an overfull node into two sets such that the
bounding boxes have minimum total area
This is a heuristic. Alternatives like minimum overlap are
possible
z Finding the “best” split is expensive, use heuristics instead
See next slide
Database System Concepts - 6th Edition 25.28 ©Silberschatz, Korth and Sudarshan
Splitting an R-Tree Node
Quadratic split divides the entries in a node into two new nodes as
follows
1. Find pair of entries with “maximum separation”
that is, the pair such that the bounding box of the two would
has the maximum wasted space (area of bounding box – sum
of areas of two entries)
2. Place these entries in two new nodes
3. Repeatedly find the entry with “maximum preference” for one of the
two new nodes, and assign the entry to that node
+ Preference of an entry to a node is the increase in area of
bounding box if the entry is added to the other node
4. Stop when half the entries have been added to one node
+ Then assign remaining entries to the other node
Cheaper linear split heuristic works in time linear in number of entries,
z Cheaper but generates slightly worse splits.
Database System Concepts - 6th Edition 25.29 ©Silberschatz, Korth and Sudarshan
Deleting in R-Trees
Deletion of an entry in an R-tree done much like a B+-tree deletion.
z In case of underfull node, borrow entries from a sibling if possible,
else merging sibling nodes
z Alternative approach removes all entries from the underfull node,
deletes the node, then reinserts all entries
Database System Concepts - 6th Edition 25.30 ©Silberschatz, Korth and Sudarshan
Multimedia Databases
Database System Concepts - 6th Edition 25.32 ©Silberschatz, Korth and Sudarshan
Multimedia Data Formats
Store and transmit multimedia data in compressed form
z JPEG and GIF the most widely used formats for image data.
z MPEG standard for video data use commonalties among a
sequence of frames to achieve a greater degree of
compression.
MPEG-1 quality comparable to VHS video tape.
z stores a minute of 30-frame-per-second video and audio in
approximately 12.5 MB
MPEG-2 designed for digital broadcast systems and digital video
disks; negligible loss of video quality.
z Compresses 1 minute of audio-video to approximately 17 MB.
Several alternatives of audio encoding
z MPEG-1 Layer 3 (MP3), RealAudio, WindowsMedia format, etc.
Database System Concepts - 6th Edition 25.33 ©Silberschatz, Korth and Sudarshan
Continuous-Media Data
Database System Concepts - 6th Edition 25.34 ©Silberschatz, Korth and Sudarshan
Video Servers
Video-on-demand systems deliver video from central video servers,
across a network, to terminals
z Must guarantee end-to-end delivery rates
Current video-on-demand servers are based on file systems; existing
database systems do not meet real-time response requirements.
Multimedia data are stored on several disks (RAID configuration), or on
tertiary storage for less frequently accessed data.
Head-end terminals - used to view multimedia data
z PCs or TVs attached to a small, inexpensive computer called a set-
top box.
Database System Concepts - 6th Edition 25.35 ©Silberschatz, Korth and Sudarshan
Similarity-Based Retrieval
Examples of similarity based retrieval
Pictorial data: Two pictures or images that are slightly different as
represented in the database may be considered the same by a user.
z E.g., identify similar designs for registering a new trademark.
Audio data: Speech-based user interfaces allow the user to give a
command or identify a data item by speaking.
z E.g., test user input against stored commands.
Handwritten data: Identify a handwritten data item or command stored
in the database
Database System Concepts - 6th Edition 25.36 ©Silberschatz, Korth and Sudarshan
Mobility
Database System Concepts - 6th Edition 25.38 ©Silberschatz, Korth and Sudarshan
Mobile Computing Environments (Cont.)
A model for mobile communication
z Mobile hosts communicate to the wired network via computers
referred to as mobile support (or base) stations.
z Each mobile support station manages those mobile hosts within its
cell.
z When mobile hosts move between cells, there is a handoff of
control from one mobile support station to another.
Direct communication, without going through a mobile support station
is also possible between nearby mobile hosts
z Supported, for e.g., by the Bluetooth standard (up to 10 meters,
atup to 721 kbps)
Database System Concepts - 6th Edition 25.39 ©Silberschatz, Korth and Sudarshan
Database Issues in Mobile Computing
Database System Concepts - 6th Edition 25.40 ©Silberschatz, Korth and Sudarshan
Routing and Query Processing
Must consider these competing costs:
z User time.
z Communication cost
Connection time - used to assign monetary charges in
some cellular systems.
Number of bytes, or packets, transferred - used to compute
charges in digital cellular systems
Time-of-day based charges - vary based on peak or off-
peak periods
z Energy - optimize use of battery power by minimizing reception
and transmission of data.
Receiving radio signals requires much less energy than
transmitting radio signals.
Database System Concepts - 6th Edition 25.41 ©Silberschatz, Korth and Sudarshan
Broadcast Data
Mobile support stations can broadcast frequently-requested data
z Allows mobile hosts to wait for needed data, rather than having to
consume energy transmitting a request
z Supports mobile hosts without transmission capability
A mobile host may optimize energy costs by determining if a query can
be answered using only cached data
z If not then must either;
Wait for the data to be broadcast
Transmit a request for data and must know when the relevant
data will be broadcast.
Broadcast data may be transmitted according to a fixed schedule or a
changeable schedule.
z For changeable schedule: the broadcast schedule must itself be
broadcast at a well-known radio frequency and at well-known time
intervals
Data reception may be interrupted by noise
z Use techniques similar to RAID to transmit redundant data (parity)
Database System Concepts - 6th Edition 25.42 ©Silberschatz, Korth and Sudarshan
Disconnectivity and Consistency
A mobile host may remain in operation during periods of
disconnection.
Problems created if the user of the mobile host issues queries and
updates on data that resides or is cached locally:
z Recoverability: Updates entered on a disconnected machine may
be lost if the mobile host fails. Since the mobile host represents a
single point of failure, stable storage cannot be simulated well.
z Consistency: Cached data may become out of date, but the
mobile host cannot discover this until it is reconnected.
Database System Concepts - 6th Edition 25.43 ©Silberschatz, Korth and Sudarshan
Mobile Updates
Partitioning via disconnection is the normal mode of operation in
mobile computing.
For data updated by only one mobile host, simple to propagate update
when mobile host reconnects
z In other cases data may become invalid and updates may conflict.
When data are updated by other computers, invalidation reports
inform a reconnected mobile host of out-of-date cache entries
z However, mobile host may miss a report.
Version-numbering-based schemes guarantee only that if two hosts
independently update the same version of a document, the clash will
be detected eventually, when the hosts exchange information either
directly or through a common host.
z More on this shortly
Automatic reconciliation of inconsistent copies of data is difficult
z Manual intervention may be needed
Database System Concepts - 6th Edition 25.44 ©Silberschatz, Korth and Sudarshan
Detecting Inconsistent Updates
Version vector scheme used to detect inconsistent updates to
documents at different hosts (sites).
Copies of document d at hosts i and j are inconsistent if
1. the copy of document d at i contains updates performed by host k
that have not been propagated to host j (k may be the same as i),
and
2. the copy of d at j contains updates performed by host l that have
not been propagated to host i (l may be the same as j)
Basic idea: each host i stores, with its copy of each document d, a
version vector - a set of version numbers, with an element Vd,i [k] for
every other host k
When a host i updates a document d, it increments the version number
Vd,i [i] by 1
Database System Concepts - 6th Edition 25.45 ©Silberschatz, Korth and Sudarshan
Detecting Inconsistent Updates (Cont.)
When two hosts i and j connect to each other they check if the copies of
all documents d that they share are consistent:
1. If the version vectors are the same on both hosts (that is, for each k,
Vd,i [k] = Vd,j [k]) then the copies of d are identical.
2. If, for each k, Vd,i [k] ≤ Vd,j [k], and the version vectors are not
identical, then the copy of document d at host i is older than the
one at host j
That is, the copy of document d at host j was obtained by one
or more modifications of the copy of d at host i.
Host i replaces its copy of d, as well as its copy of the version
vector for d, with the copies from host j.
3. If there is a pair of hosts k and m such that Vd,i [k]< Vd,j [k], and
Vd,i [m] > Vd,j [m], then the copies are inconsistent
That is, two or more updates have been performed
on d independently.
Database System Concepts - 6th Edition 25.46 ©Silberschatz, Korth and Sudarshan
Handling Inconsistent Updates
Dealing with inconsistent updates is hard in general. Manual
intervention often required to merge the updates.
Version vector schemes
z were developed to deal with failures in a distributed file system,
where inconsistencies are rare.
z are used to maintain a unified file system between a fixed host and
a mobile computer, where updates at the two hosts have to be
merged periodically.
Also used for similar purposes in groupware systems.
z are used in database systems where mobile users may need to
perform transactions.
In this case, a “document” may be a single record.
Inconsistencies must either be very rare, or fall in special cases that are
easy to deal with in most cases
Database System Concepts - 6th Edition 25.47 ©Silberschatz, Korth and Sudarshan
End of Chapter
Database System Concepts - 6th Edition 25.49 ©Silberschatz, Korth and Sudarshan
Figure 25.03
Database System Concepts - 6th Edition 25.50 ©Silberschatz, Korth and Sudarshan
Figure 25.04
Database System Concepts - 6th Edition 25.51 ©Silberschatz, Korth and Sudarshan
Figure 25.05
Database System Concepts - 6th Edition 25.52 ©Silberschatz, Korth and Sudarshan
Figure 25.06
Database System Concepts - 6th Edition 25.53 ©Silberschatz, Korth and Sudarshan