Fabio Grandi Alma Mater Studiorum – Università di Bologna

Slides:



Advertisements
Similar presentations
Relational Database and Data Modeling
Advertisements

Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 5 More SQL: Complex Queries, Triggers, Views, and Schema Modification.
How did we get here? (CMIS v0.5) F2F, January 2009.
Database Management Systems, R. Ramakrishnan and J. Gehrke1 The Relational Model Chapter 3.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Relational Algebra Chapter 4, Part A Modified by Donghui Zhang.
INFS614, Fall 08 1 Relational Algebra Lecture 4. INFS614, Fall 08 2 Relational Query Languages v Query languages: Allow manipulation and retrieval of.
CMPT 354, Simon Fraser University, Fall 2008, Martin Ester 28 Database Systems I The Relational Data Model.
CMPT 354, Simon Fraser University, Fall 2008, Martin Ester 52 Database Systems I Relational Algebra.
A First Attempt towards a Logical Model for the PBMS PANDA Meeting, Milano, 18 April 2002 National Technical University of Athens Patterns for Next-Generation.
Database Management Systems, R. Ramakrishnan and J. Gehrke1 Relational Algebra Chapter 4, Part A.
Database Systems More SQL Database Design -- More SQL1.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Rutgers University Relational Algebra 198:541 Rutgers University.
The Relational Model Codd (1970): based on set theory Relational model: represents the database as a collection of relations (a table of values --> file)
Chapter 12 Information Systems. 2 Chapter Goals Define the role of general information systems Explain how spreadsheets are organized Create spreadsheets.
RIZWAN REHMAN, CCS, DU. Advantages of ORDBMSs  The main advantages of extending the relational data model come from reuse and sharing.  Reuse comes.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Information storage: Introduction of database 10/7/2004 Xiangming Mu.
Chapter 4 The Relational Model.
CSE314 Database Systems More SQL: Complex Queries, Triggers, Views, and Schema Modification Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
Introduction to SQL Steve Perry
Entity Framework Overview. Entity Framework A set of technologies in ADO.NET that support the development of data-oriented software applications A component.
FEN  Data Definition: CREATE TABLE, ALTER TABLE  Data Manipulation: INSERT, UPDATE, DELETE  Queries: SELECT SQL: Structured Query Language.
FEN Introduction to the database field:  The Relational Model Seminar: Introduction to relational databases.
1.1 CAS CS 460/660 Introduction to Database Systems Relational Algebra.
ICS 321 Fall 2011 The Relational Model of Data (i) Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 8/29/20111Lipyeow.
SE305 Database System Technology 23/10/2014 Quiz-2.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 4-1 Relational Databases.
Object storage and object interoperability
Jennifer Widom Relational Databases The Relational Model.
Lecture 15: Query Optimization. Very Big Picture Usually, there are many possible query execution plans. The optimizer is trying to chose a good one.
Introduction to ORM Hibernate Hibernate vs JDBC. May 12, 2011 INTRODUCTION TO ORM ORM is a programming technique for converting data between relational.
Chapter 3 The Relational Model. Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. “Legacy.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 The Relational Model Chapter 3.
1 CS122A: Introduction to Data Management Lecture #4 (E-R  Relational Translation) Instructor: Chen Li.
CENG 351 File Structures and Data Management1 Relational Model Chapter 3.
Fundamental of Database Systems
Introduction to Spatial Computing CSE 555
More SQL: Complex Queries, Triggers, Views, and Schema Modification
Databases and DBMSs Todd S. Bacastow January
Chapter (12) – Old Version
21st International Symposium on Temporal Representation and Reasoning
A Generalized Modeling Framework for Schema Versioning Support
Relational Data Model Lu Chaojun, SJTU.
Introduction to Databases
Oracle & SQL Introduction
The Object-Oriented Database System Manifesto
Light-weight Ontology Versioning with Multi-temporal RDF Schema
Dynamic Multi-version Ontology-based Personalization
Quiz Questions Q.1 An entity set that does not have sufficient attributes to form a primary key is a (A) strong entity set. (B) weak entity set. (C) simple.
Databases and Database Management Systems Chapter 9
Chapter 4 Relational Databases
The Valid Ontology: a simple OWL Temporal Versioning Framework
Relational Algebra Chapter 4, Part A
Translation of ER-diagram into Relational Schema
 DATAABSTRACTION  INSTANCES& SCHEMAS  DATA MODELS.
Relational Algebra 461 The slides for this text are organized into chapters. This lecture covers relational algebra, from Chapter 4. The relational calculus.
File Systems and Databases
The Relational Model Relational Data Model
Relational Databases The Relational Model.
Relational Databases The Relational Model.
Multi-temporal RDF Ontology Versioning
Electrical and Computer Engineering Department
Data Model.
Query Optimization.
Chapter 11 Managing Databases with SQL Server 2000
Database SQL.
The Relational Data Model
Practical Database Design and Tuning Objectives
Presentation transcript:

Fabio Grandi Alma Mater Studiorum – Università di Bologna A Relational Multi-Schema Data Model and Query Language for Full Support of Schema Versioning Fabio Grandi Alma Mater Studiorum – Università di Bologna SEBD 2002

Introduction Schema Evolution Schema Versioning Automatic recovery of extant data after schema changes Schema Versioning Maintenance of past schemas (e.g. for legacy application support) Two design options for the implementation of data repositories SEBD 2002

Design Options for Extant Data Single-pool solution Roddick, Roddick & Snodgrass [TSQL2 ’95] All schema versions associated with a unique shared data repository Multi-pool solution De Castro, Grandi & Scalas [TDB ’95, IS ’97] Each schema version associated with a different private data repository SEBD 2002

Single-pool - Example A 123 B A 125 B C create schema SV1 create table R(A int, B int) create schema SV2 alter table R add column C int A 123 B A 125 B C SV1: R(A,B) SV1: R(A,B) SV2: R(A,B,C) SEBD 2002

Single-pool - Example (2) create schema SV3 alter table R drop column B create schema SV4 alter table R alter column A char A 125 B C A’ 125 B C A’’ xy SV1: R(A,B) SV2: R(A,B,C) SV3: R(A,C) SV1: R(A,B) <= R(A’,B) SV2: R(A,B,C) <= R(A’,B,C) SV3: R(A,C) <= R(A’,C) SV4: R(A,C) <= R(A’’,C) SEBD 2002

Multi-pool - Example A 123 B A 125 B C 33 DP1: DP2: A 125 C 55 A xy C SV1: R(A,B) SV2: R(A,B,C) A 125 C 55 A xy C 44 DP3: DP4: SV3: R(A,C) SV4: R(A,C) SEBD 2002

Single-pool vs Multi-pool Simple to implement with the completed schema solution Reduces to a quite “trivial” view mechanism Multi-pool: More flexible and complex Thus, potentially more useful, but… Is it feasible ? And what’s for ? SEBD 2002

Multi-pool – what’s for? From a conceptual perspective different schema versions correspond to different points of view SV2 SV1 SV3 SV4 Application Domain SEBD 2002

Schema Versions as Viewpoints IT Market US Market EU Market Different viewpoints on the same data involve different structures at intensional level (schema) different values at extensional level (data) SEBD 2002

A Concrete Example The “Lark 2.5” car model in the global market ( diff. viewpoints involve diff. marketing strategies ) Lark 2.5 26 K$ US Market Lark 2.5 32 K€ Euro4 EU Market Lark GT 31 K€ Euro3 IT Market SEBD 2002

A Multi-schema Query Language Full potentialities of a multi-pool schema versioning approach can be exploited only by means of a query language which allows users/developers to express Multi-schema Queries that is involving data belonging to different data pools MSQL - Multi-schema SQL extension SEBD 2002

The MSQL Query Language MSQL basic construct: contextualization of names and data references to schema versions [SV: X] denotes the conceptual entity named “X” in schema version “SV” SV: X denotes the extension wrt schema version “SV” of the conceptual entity “X” the two mechanisms can be combined (e.g. as in SVi: [SVj: X] ) SEBD 2002

The MSQL Query Language (2) Examples: select * from [SVj: R] retrieve the table called R in SVj select * from SVi: R retrieve the contents wrt SVi of R select * from SVi: [SVj: R] retrieve the contents wrt SVi of the table called R in SVj SEBD 2002

The MSQL Query Language (3) Examples: select [SVj: A] from R retrieve the column called A in SVj of R select SVi: A from R retrieve the contents wrt SVi of R.A select SVi: [SVj: A] from R retrieve the contents wrt SVi of the column called A in SVj of R SEBD 2002

The MSQL Query Language (4) Example: select SVi: [SVj: A] from SVk: [SVl: R] retrieve the values wrt SVi of the column called A in SVj in the tuples belonging wrt SVk to the table called R in SVl SEBD 2002

The MSQL Query Language (5) Example: set schema USMKT; select NAME from EUMKT:CAR as EC, ITMKT:CAR as IC where IC.PRICE < EC.PRICE retrieve the American names of all the cars also sold in Europe such that the Italian price is lower than the price applied in the rest of Europe SEBD 2002

The Logical Storage Model Provides a simple implementation scheme for a Multi-pool schema versioning database (on top of a traditional relational DBMS) Is used to formally define the semantics of the MSQL language Representation of the SVi data pool: RNamei(RID,Name) ANamei(AID,Name) RSchemai(RID,AID) RExti(RID,TID) AExti(TID,AID,Value) SEBD 2002

Conclusions Defense of the Multi-pool approach (from a conceptual design standpoint) Introduction of the Multi-schema Query Language (MSQL) Introduction of the Logical Storage Model Future Work development of implementation strategies study of formal properties (e.g. correctness of a schema evolution process under the multi-pool approach) SEBD 2002