View Management System in Object_Oriented Databases
碩士 === 國立中央大學 === 資訊及電子工程研究所 === 82 === Althohgh there are many researches on the design and manufacture of view management systems in OODB in recent years, many difficulties still exist. This paper aims at designing a view mana...
Main Authors: | , |
---|---|
Other Authors: | |
Format: | Others |
Language: | zh-TW |
Published: |
1994
|
Online Access: | http://ndltd.ncl.edu.tw/handle/27031497528344028749 |
id |
ndltd-TW-082NCU00393003 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-TW-082NCU003930032016-07-18T04:09:42Z http://ndltd.ncl.edu.tw/handle/27031497528344028749 View Management System in Object_Oriented Databases 物件導向資料庫之景觀管理系統 Cheng_Pen Wu 吳正本 碩士 國立中央大學 資訊及電子工程研究所 82 Althohgh there are many researches on the design and manufacture of view management systems in OODB in recent years, many difficulties still exist. This paper aims at designing a view management system in OODB : AMV(Advanced MultiView), and tries to solve the problems other existent systems often encounter. There are four major problems : (1) How can the system integrate the new virtual class defined by view definers into the class hierarchy of the database ? How can this integration be done by the system automatically to avert the data inconsistency due to users' neglect? (2) How can these views be reused to a large extent? (3) How do these operators designed for define views operate on the whole class hierarchy but not just a single class? (4) How can we reduce the system load when creating views? For the purpose of simplifying the definition and management of views, we divede the view creating process into four phases : (1) deriving virtual class phases, (2) integrating global schema phase, (3) selecting view class phase, (4) creating view schema phase. AMV has been implemented successfully in ONTOS OODBMS. By the time of implementation,we divede the view system architecture into four levels : Meta_Schema Level, Physical_Schema Level, Logical_Schema Level, and Objects Level. The first two are the physical database, that explain the real saving status of data in the database. The last two levells are the logical database whose logical status can be seen by users. Through the system level separation, the system can be unbrudened of the heavy load of the view structure reorganization. The design and implementation methods of view management system in AMV are simple and common. We need neither the expansion of traditional object_oriented concepts, nor the special functions offered by DBMS. AMV can be transplanted easily to other well-developed OODB. Baw_Jhiune Liu & Joung_Choung Houng 劉寶鈞 洪炯宗 1994 學位論文 ; thesis 93 zh-TW |
collection |
NDLTD |
language |
zh-TW |
format |
Others
|
sources |
NDLTD |
description |
碩士 === 國立中央大學 === 資訊及電子工程研究所 === 82 === Althohgh there are many researches on the design and
manufacture of view management systems in OODB in recent
years, many difficulties still exist. This paper aims at
designing a view management system in OODB : AMV(Advanced
MultiView), and tries to solve the problems other existent
systems often encounter. There are four major problems : (1)
How can the system integrate the new virtual class defined by
view definers into the class hierarchy of the database ? How
can this integration be done by the system automatically to
avert the data inconsistency due to users' neglect? (2) How
can these views be reused to a large extent? (3) How do these
operators designed for define views operate on the whole class
hierarchy but not just a single class? (4) How can we reduce
the system load when creating views? For the purpose of
simplifying the definition and management of views, we divede
the view creating process into four phases : (1) deriving
virtual class phases, (2) integrating global schema phase, (3)
selecting view class phase, (4) creating view schema phase. AMV
has been implemented successfully in ONTOS OODBMS. By the time
of implementation,we divede the view system architecture into
four levels : Meta_Schema Level, Physical_Schema Level,
Logical_Schema Level, and Objects Level. The first two are the
physical database, that explain the real saving status of data
in the database. The last two levells are the logical database
whose logical status can be seen by users. Through the system
level separation, the system can be unbrudened of the heavy
load of the view structure reorganization. The design and
implementation methods of view management system in AMV are
simple and common. We need neither the expansion of traditional
object_oriented concepts, nor the special functions offered by
DBMS. AMV can be transplanted easily to other well-developed
OODB.
|
author2 |
Baw_Jhiune Liu & Joung_Choung Houng |
author_facet |
Baw_Jhiune Liu & Joung_Choung Houng Cheng_Pen Wu 吳正本 |
author |
Cheng_Pen Wu 吳正本 |
spellingShingle |
Cheng_Pen Wu 吳正本 View Management System in Object_Oriented Databases |
author_sort |
Cheng_Pen Wu |
title |
View Management System in Object_Oriented Databases |
title_short |
View Management System in Object_Oriented Databases |
title_full |
View Management System in Object_Oriented Databases |
title_fullStr |
View Management System in Object_Oriented Databases |
title_full_unstemmed |
View Management System in Object_Oriented Databases |
title_sort |
view management system in object_oriented databases |
publishDate |
1994 |
url |
http://ndltd.ncl.edu.tw/handle/27031497528344028749 |
work_keys_str_mv |
AT chengpenwu viewmanagementsysteminobjectorienteddatabases AT wúzhèngběn viewmanagementsysteminobjectorienteddatabases AT chengpenwu wùjiàndǎoxiàngzīliàokùzhījǐngguānguǎnlǐxìtǒng AT wúzhèngběn wùjiàndǎoxiàngzīliàokùzhījǐngguānguǎnlǐxìtǒng |
_version_ |
1718352132934991872 |