Relation-Aware Schema Encoding and Linking for Text-To-SQL Parsers

Total Page:16

File Type:pdf, Size:1020Kb

Relation-Aware Schema Encoding and Linking for Text-To-SQL Parsers RAT-SQL: Relation-Aware Schema Encoding and Linking for Text-to-SQL Parsers Bailin Wang∗y Richard Shin∗z University of Edinburgh UC Berkeley [email protected] [email protected] Xiaodong Liu Oleksandr Polozov Matthew Richardson Microsoft Research, Redmond {xiaodl,polozov,mattri}@microsoft.com Abstract 2018), new tasks such as WikiSQL (Zhong et al., 2017) and Spider (Yu et al., 2018b) pose the real- When translating natural language questions life challenge of generalization to unseen database into SQL queries to answer questions from a schemas. Every query is conditioned on a multi- database, contemporary semantic parsing mod- els struggle to generalize to unseen database table database schema, and the databases do not schemas. The generalization challenge lies overlap between the train and test sets. in (a) encoding the database relations in an Schema generalization is challenging for three accessible way for the semantic parser, and interconnected reasons. First, any text-to-SQL pars- (b) modeling alignment between database ing model must encode the schema into representa- columns and their mentions in a given query. tions suitable for decoding a SQL query that might We present a unified framework, based on the involve the given columns or tables. Second, these relation-aware self-attention mechanism, to address schema encoding, schema linking, and representations should encode all the information feature representation within a text-to-SQL about the schema such as its column types, foreign encoder. On the challenging Spider dataset key relations, and primary keys used for database this framework boosts the exact match accu- joins. Finally, the model must recognize NL used racy to 57.2%, surpassing its best counterparts to refer to columns and tables, which might differ by 8.7% absolute improvement. Further from the referential language seen in training. The augmented with BERT, it achieves the new latter challenge is known as schema linking – align- state-of-the-art performance of 65.6% on the ing entity references in the question to the intended Spider leaderboard. In addition, we observe qualitative improvements in the model’s un- schema columns or tables. derstanding of schema linking and alignment. While the question of schema encoding has been Our implementation will be open-sourced at studied in recent literature (Bogin et al., 2019a), https://github.com/Microsoft/rat-sql. schema linking has been relatively less explored. Consider the example in Figure1. It illustrates the 1 Introduction challenge of ambiguity in linking: while “model” The ability to effectively query databases with nat- in the question refers to car_names.model ural language (NL) unlocks the power of large rather than model_list.model, “cars” actu- datasets to the vast majority of users who are not ally refers to both cars_data and car_names proficient in query languages. As such, a large (but not car_makers) for the purpose of table body of research has focused on the task of trans- joining. To resolve the column/table references lating NL questions into SQL queries that existing properly, the semantic parser must take into ac- database software can execute. count both the known schema relations (e.g. foreign The development of large annotated datasets of keys) and the question context. questions and the corresponding SQL queries has Prior work (Bogin et al., 2019a) addressed the catalyzed progress in the field. In contrast to prior schema representation problem by encoding the di- semantic parsing datasets (Finegan-Dollak et al., rected graph of foreign key relations in the schema with a graph neural network (GNN). While effec- ∗ Equal contribution. Order decided by a coin toss. tive, this approach has two important shortcomings. y Work done during an internship at Microsoft Research. z Work done while partly affiliated with Microsoft Re- First, it does not contextualize schema encoding search. Now at Microsoft: [email protected]. with the question, thus making reasoning about 7567 Proceedings of the 58th Annual Meeting of the Association for Computational Linguistics, pages 7567–7578 July 5 - 10, 2020. c 2020 Association for Computational Linguistics Natural Language Question: Desired SQL: For the cars with 4 cylinders, which model has the largest horsepower? SELECT T1.model FROM car_names AS T1 JOIN cars_data AS T2 Schema: ON T1.make_id = T2.id cars_data WHERE T2.cylinders = 4 … ORDER BY T2.horsepower DESC LIMIT 1 id mpg cylinders edispl horsepower weight accelerate year car_names model_list car_makers Question → Column linking (unknown) Question → Table linking (unknown) make_id model make model_id maker model id maker full_name country Column → Column foreign keys (known) Figure 1: A challenging text-to-SQL task from the Spider dataset. schema linking difficult after both the column rep- 2019) achieves a test set accuracy of 91.8%, signif- resentations and question word representations are icantly higher than the state of the art on Spider. built. Second, it limits information propagation The recent state-of-the-art models evaluated on during schema encoding to the predefined graph of Spider use various attentional architectures for foreign key relations. The advent of self-attentional question/schema encoding and AST-based struc- mechanisms in NLP (Vaswani et al., 2017) shows tural architectures for query decoding. IRNet (Guo that global reasoning is crucial to effective repre- et al., 2019) encodes the question and schema sep- sentations of relational structures. However, we arately with LSTM and self-attention respectively, would like any global reasoning to still take into augmenting them with custom type vectors for account the aforementioned schema relations. schema linking. They further use the AST-based de- In this work, we present a unified framework, coder of Yin and Neubig(2017) to decode a query 1 called RAT-SQL, for encoding relational structure in an intermediate representation (IR) that exhibits in the database schema and a given question. It uses higher-level abstractions than SQL. Bogin et al. relation-aware self-attention to combine global rea- (2019a) encode the schema with a GNN and a simi- soning over the schema entities and question words lar grammar-based decoder. Both works emphasize with structured reasoning over predefined schema schema encoding and schema linking, but design relations. We then apply RAT-SQL to the problems separate featurization techniques to augment word of schema encoding and schema linking. As a re- vectors (as opposed to relations between words and sult, we obtain 57.2% exact match accuracy on the columns) to resolve it. In contrast, the RAT-SQL Spider test set. At the time of writing, this result framework provides a unified way to encode arbi- is the state of the art among models unaugmented trary relational information among inputs. with pretrained BERT embeddings – and further Concurrently with this work, Bogin et al. reaches to the overall state of the art (65.6%) when (2019b) published Global-GNN, a different ap- RAT-SQL is augmented with BERT. In addition, proach to schema linking for Spider, which ap- we experimentally demonstrate that RAT-SQL en- plies global reasoning between question words and ables the model to build more accurate internal schema columns/tables. Global reasoning is imple- representations of the question’s true alignment mented by gating the GNN that encodes the schema with schema columns and tables. using the question token representations. This dif- 2 Related Work fers from RAT-SQL in two important ways: (a) question word representations influence the schema Semantic parsing of NL to SQL recently surged representations but not vice versa, and (b) like in in popularity thanks to the creation of two new other GNN-based encoders, message propagation multi-table datasets with the challenge of schema is limited to the schema-induced edges such as for- generalization – WikiSQL (Zhong et al., 2017) and eign key relations. In contrast, our relation-aware Spider (Yu et al., 2018b). Schema encoding is not transformer mechanism allows encoding arbitrary as challenging in WikiSQL as in Spider because relations between question words and schema ele- it lacks multi-table relations. Schema linking is ments explicitly, and these representations are com- relevant for both tasks but also more challenging in puted jointly over all inputs using self-attention. Spider due to the richer NL expressiveness and less We use the same formulation of relation-aware restricted SQL grammar observed in it. The state self-attention as Shaw et al.(2018). However, they of the art semantic parser on WikiSQL (He et al., only apply it to sequences of words in the context 1Relation-Aware Transformer. of machine translation, and as such, their relation 7568 types only encode the relative distance between two computes a learned relation between all the in- words. We extend their work and show that relation- put elements xi, and the strength of this relation (h) aware self-attention can effectively encode more is encoded in the attention weights αij . How- complex relationships within an unordered set of ever, in many applications (including text-to-SQL elements (in our case, columns and tables within a parsing) we are aware of some preexisting rela- database schema as well as relations between the tional features between the inputs, and would like schema and the question). To the best of our knowl- to bias our encoder model toward them. This is edge, this is the first application of relation-aware straightforward for non-relational features (repre- self-attention to joint representation learning with sented directly in each xi). We could limit the at- both predefined and softly induced relations in the tention computation only to the “hard” edges where input structure. Hellendoorn et al.(2020) develop the preexisting relations are known to hold. This a similar model concurrently with this work, where would make the model similar to a graph atten- they use relation-aware self-attention to encode tion network (Velickoviˇ c´ et al., 2018), and would data flow structure in source code embeddings.
Recommended publications
  • CHAPTER 3 - Relational Database Modeling
    DATABASE SYSTEMS Introduction to Databases and Data Warehouses, Edition 2.0 CHAPTER 3 - Relational Database Modeling Copyright (c) 2020 Nenad Jukic and Prospect Press MAPPING ER DIAGRAMS INTO RELATIONAL SCHEMAS ▪ Once a conceptual ER diagram is constructed, a logical ER diagram is created, and then it is subsequently mapped into a relational schema (collection of relations) Conceptual Model Logical Model Schema Jukić, Vrbsky, Nestorov, Sharma – Database Systems Copyright (c) 2020 Nenad Jukic and Prospect Press Chapter 3 – Slide 2 INTRODUCTION ▪ Relational database model - logical database model that represents a database as a collection of related tables ▪ Relational schema - visual depiction of the relational database model – also called a logical model ▪ Most contemporary commercial DBMS software packages, are relational DBMS (RDBMS) software packages Jukić, Vrbsky, Nestorov, Sharma – Database Systems Copyright (c) 2020 Nenad Jukic and Prospect Press Chapter 3 – Slide 3 INTRODUCTION Terminology Jukić, Vrbsky, Nestorov, Sharma – Database Systems Copyright (c) 2020 Nenad Jukic and Prospect Press Chapter 3 – Slide 4 INTRODUCTION ▪ Relation - table in a relational database • A table containing rows and columns • The main construct in the relational database model • Every relation is a table, not every table is a relation Jukić, Vrbsky, Nestorov, Sharma – Database Systems Copyright (c) 2020 Nenad Jukic and Prospect Press Chapter 3 – Slide 5 INTRODUCTION ▪ Relation - table in a relational database • In order for a table to be a relation the following conditions must hold: o Within one table, each column must have a unique name. o Within one table, each row must be unique. o All values in each column must be from the same (predefined) domain.
    [Show full text]
  • Relational Query Languages
    Relational Query Languages Universidad de Concepcion,´ 2014 (Slides adapted from Loreto Bravo, who adapted from Werner Nutt who adapted them from Thomas Eiter and Leonid Libkin) Bases de Datos II 1 Databases A database is • a collection of structured data • along with a set of access and control mechanisms We deal with them every day: • back end of Web sites • telephone billing • bank account information • e-commerce • airline reservation systems, store inventories, library catalogs, . Relational Query Languages Bases de Datos II 2 Data Models: Ingredients • Formalisms to represent information (schemas and their instances), e.g., – relations containing tuples of values – trees with labeled nodes, where leaves contain values – collections of triples (subject, predicate, object) • Languages to query represented information, e.g., – relational algebra, first-order logic, Datalog, Datalog: – tree patterns – graph pattern expressions – SQL, XPath, SPARQL Bases de Datos II 3 • Languages to describe changes of data (updates) Relational Query Languages Questions About Data Models and Queries Given a schema S (of a fixed data model) • is a given structure (FOL interpretation, tree, triple collection) an instance of the schema S? • does S have an instance at all? Given queries Q, Q0 (over the same schema) • what are the answers of Q over a fixed instance I? • given a potential answer a, is a an answer to Q over I? • is there an instance I where Q has an answer? • do Q and Q0 return the same answers over all instances? Relational Query Languages Bases de Datos II 4 Questions About Query Languages Given query languages L, L0 • how difficult is it for queries in L – to evaluate such queries? – to check satisfiability? – to check equivalence? • for every query Q in L, is there a query Q0 in L0 that is equivalent to Q? Bases de Datos II 5 Research Questions About Databases Relational Query Languages • Incompleteness, uncertainty – How can we represent incomplete and uncertain information? – How can we query it? .
    [Show full text]
  • The Relational Data Model and Relational Database Constraints
    chapter 33 The Relational Data Model and Relational Database Constraints his chapter opens Part 2 of the book, which covers Trelational databases. The relational data model was first introduced by Ted Codd of IBM Research in 1970 in a classic paper (Codd 1970), and it attracted immediate attention due to its simplicity and mathematical foundation. The model uses the concept of a mathematical relation—which looks somewhat like a table of values—as its basic building block, and has its theoretical basis in set theory and first-order predicate logic. In this chapter we discuss the basic characteristics of the model and its constraints. The first commercial implementations of the relational model became available in the early 1980s, such as the SQL/DS system on the MVS operating system by IBM and the Oracle DBMS. Since then, the model has been implemented in a large num- ber of commercial systems. Current popular relational DBMSs (RDBMSs) include DB2 and Informix Dynamic Server (from IBM), Oracle and Rdb (from Oracle), Sybase DBMS (from Sybase) and SQLServer and Access (from Microsoft). In addi- tion, several open source systems, such as MySQL and PostgreSQL, are available. Because of the importance of the relational model, all of Part 2 is devoted to this model and some of the languages associated with it. In Chapters 4 and 5, we describe the SQL query language, which is the standard for commercial relational DBMSs. Chapter 6 covers the operations of the relational algebra and introduces the relational calculus—these are two formal languages associated with the relational model.
    [Show full text]
  • SQL Vs Nosql: a Performance Comparison
    SQL vs NoSQL: A Performance Comparison Ruihan Wang Zongyan Yang University of Rochester University of Rochester [email protected] [email protected] Abstract 2. ACID Properties and CAP Theorem We always hear some statements like ‘SQL is outdated’, 2.1. ACID Properties ‘This is the world of NoSQL’, ‘SQL is still used a lot by We need to refer the ACID properties[12]: most of companies.’ Which one is accurate? Has NoSQL completely replace SQL? Or is NoSQL just a hype? SQL Atomicity (Structured Query Language) is a standard query language A transaction is an atomic unit of processing; it should for relational database management system. The most popu- either be performed in its entirety or not performed at lar types of RDBMS(Relational Database Management Sys- all. tems) like Oracle, MySQL, SQL Server, uses SQL as their Consistency preservation standard database query language.[3] NoSQL means Not A transaction should be consistency preserving, meaning Only SQL, which is a collection of non-relational data stor- that if it is completely executed from beginning to end age systems. The important character of NoSQL is that it re- without interference from other transactions, it should laxes one or more of the ACID properties for a better perfor- take the database from one consistent state to another. mance in desired fields. Some of the NOSQL databases most Isolation companies using are Cassandra, CouchDB, Hadoop Hbase, A transaction should appear as though it is being exe- MongoDB. In this paper, we’ll outline the general differences cuted in iso- lation from other transactions, even though between the SQL and NoSQL, discuss if Relational Database many transactions are execut- ing concurrently.
    [Show full text]
  • Relational Algebra and SQL Relational Query Languages
    Relational Algebra and SQL Chapter 5 1 Relational Query Languages • Languages for describing queries on a relational database • Structured Query Language (SQL) – Predominant application-level query language – Declarative • Relational Algebra – Intermediate language used within DBMS – Procedural 2 1 What is an Algebra? · A language based on operators and a domain of values · Operators map values taken from the domain into other domain values · Hence, an expression involving operators and arguments produces a value in the domain · When the domain is a set of all relations (and the operators are as described later), we get the relational algebra · We refer to the expression as a query and the value produced as the query result 3 Relational Algebra · Domain: set of relations · Basic operators: select, project, union, set difference, Cartesian product · Derived operators: set intersection, division, join · Procedural: Relational expression specifies query by describing an algorithm (the sequence in which operators are applied) for determining the result of an expression 4 2 The Role of Relational Algebra in a DBMS 5 Select Operator • Produce table containing subset of rows of argument table satisfying condition σ condition (relation) • Example: σ Person Hobby=‘stamps’(Person) Id Name Address Hobby Id Name Address Hobby 1123 John 123 Main stamps 1123 John 123 Main stamps 1123 John 123 Main coins 9876 Bart 5 Pine St stamps 5556 Mary 7 Lake Dr hiking 9876 Bart 5 Pine St stamps 6 3 Selection Condition • Operators: <, ≤, ≥, >, =, ≠ • Simple selection
    [Show full text]
  • Plantuml Language Reference Guide
    Drawing UML with PlantUML Language Reference Guide (Version 5737) PlantUML is an Open Source project that allows to quickly write: • Sequence diagram, • Usecase diagram, • Class diagram, • Activity diagram, • Component diagram, • State diagram, • Object diagram. Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples Every UML description must start by @startuml and must finish by @enduml. The sequence ”->” is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use ”-->”. It is also possible to use ”<-” and ”<--”. That does not change the drawing, but may improve readability. Example: @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: another authentication Response @enduml To use asynchronous message, you can use ”->>” or ”<<-”. @startuml Alice -> Bob: synchronous call Alice ->> Bob: asynchronous call @enduml PlantUML : Language Reference Guide, December 11, 2010 (Version 5737) 1 of 96 1.2 Declaring participant 1 SEQUENCE DIAGRAM 1.2 Declaring participant It is possible to change participant order using the participant keyword. It is also possible to use the actor keyword to use a stickman instead of a box for the participant. You can rename a participant using the as keyword. You can also change the background color of actor or participant, using html code or color name. Everything that starts with simple quote ' is a comment. @startuml actor Bob #red ' The only difference between actor and participant is the drawing participant Alice participant "I have a really\nlong name" as L #99FF99 Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml PlantUML : Language Reference Guide, December 11, 2010 (Version 5737) 2 of 96 1.3 Use non-letters in participants 1 SEQUENCE DIAGRAM 1.3 Use non-letters in participants You can use quotes to define participants.
    [Show full text]
  • A Developer's Guide to Data Modeling for SQL Server
    Praise for A Developer’s Guide to Data Modeling for SQL Server “Eric and Joshua do an excellent job explaining the importance of data modeling and how to do it correctly. Rather than relying only on academic concepts, they use real-world ex- amples to illustrate the important concepts that many database and application develop- ers tend to ignore. The writing style is conversational and accessible to both database design novices and seasoned pros alike. Readers who are responsible for designing, imple- menting, and managing databases will benefit greatly from Joshua’s and Eric’s expertise.” —Anil Desai, Consultant, Anil Desai, Inc. “Almost every IT project involves data storage of some kind, and for most that means a relational database management system (RDBMS). This book is written for a database- centric audience (database modelers, architects, designers, developers, etc.). The authors do a great job of showing us how to take a project from its initial stages of requirements gathering all the way through to implementation. Along the way we learn how to handle some of the real-world design issues that typically surface as we go through the process. “The bottom line here is simple. This is the book you want to have just finished read- ing when your boss says ‘We have a new project I would like your help with.’” —Ronald Landers, Technical Consultant, IT Professionals, Inc. “The Data Model is the foundation of the application. I’m pleased to see additional books being written to address this critical phase. This book presents a balanced and pragmatic view with the right priorities to get your SQL server project off to a great start and a long life.” —Paul Nielsen, SQL Server MVP, SQLServerBible.com “This is a truly excellent introduction to the database design methodology that will work for both novices and advanced designers.
    [Show full text]
  • Fast Foreign-Key Detection in Microsoft SQL
    Fast Foreign-Key Detection in Microsoft SQL Server PowerPivot for Excel Zhimin Chen Vivek Narasayya Surajit Chaudhuri Microsoft Research Microsoft Research Microsoft Research [email protected] [email protected] [email protected] ABSTRACT stored in a relational database, which they can import into Excel. Microsoft SQL Server PowerPivot for Excel, or PowerPivot for Other sources of data are text files, web data feeds or in general any short, is an in-memory business intelligence (BI) engine that tabular data range imported into Excel. enables Excel users to interactively create pivot tables over large data sets imported from sources such as relational databases, text files and web data feeds. Unlike traditional pivot tables in Excel that are defined on a single table, PowerPivot allows analysis over multiple tables connected via foreign-key joins. In many cases however, these foreign-key relationships are not known a priori, and information workers are often not be sophisticated enough to define these relationships. Therefore, the ability to automatically discover foreign-key relationships in PowerPivot is valuable, if not essential. The key challenge is to perform this detection interactively and with high precision even when data sets scale to hundreds of millions of rows and the schema contains tens of tables and hundreds of columns. In this paper, we describe techniques for fast foreign-key detection in PowerPivot and experimentally evaluate its accuracy, performance and scale on both synthetic benchmarks and real-world data sets. These techniques have been incorporated into PowerPivot for Excel. Figure 1. Example of pivot table in Excel. It enables multi- dimensional analysis over a single table.
    [Show full text]
  • Session 5 – Main Theme
    Database Systems Session 5 – Main Theme Relational Algebra, Relational Calculus, and SQL Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences Presentation material partially based on textbook slides Fundamentals of Database Systems (6th Edition) by Ramez Elmasri and Shamkant Navathe Slides copyright © 2011 and on slides produced by Zvi Kedem copyight © 2014 1 Agenda 1 Session Overview 2 Relational Algebra and Relational Calculus 3 Relational Algebra Using SQL Syntax 5 Summary and Conclusion 2 Session Agenda . Session Overview . Relational Algebra and Relational Calculus . Relational Algebra Using SQL Syntax . Summary & Conclusion 3 What is the class about? . Course description and syllabus: » http://www.nyu.edu/classes/jcf/CSCI-GA.2433-001 » http://cs.nyu.edu/courses/fall11/CSCI-GA.2433-001/ . Textbooks: » Fundamentals of Database Systems (6th Edition) Ramez Elmasri and Shamkant Navathe Addition Wesley ISBN-10: 0-1360-8620-9, ISBN-13: 978-0136086208 6th Edition (04/10) 4 Icons / Metaphors Information Common Realization Knowledge/Competency Pattern Governance Alignment Solution Approach 55 Agenda 1 Session Overview 2 Relational Algebra and Relational Calculus 3 Relational Algebra Using SQL Syntax 5 Summary and Conclusion 6 Agenda . Unary Relational Operations: SELECT and PROJECT . Relational Algebra Operations from Set Theory . Binary Relational Operations: JOIN and DIVISION . Additional Relational Operations . Examples of Queries in Relational Algebra . The Tuple Relational Calculus . The Domain Relational Calculus 7 The Relational Algebra and Relational Calculus . Relational algebra . Basic set of operations for the relational model . Relational algebra expression . Sequence of relational algebra operations . Relational calculus . Higher-level declarative language for specifying relational queries 8 Unary Relational Operations: SELECT and PROJECT (1/3) .
    [Show full text]
  • Mssql Database Schema Diagram
    Mssql Database Schema Diagram Unconcealing Hendrik sometimes lown his love-tokens inestimably and amalgamating so scantly! Forkiest and evidentiary Tod pacifying his Calder bespeaks roll widdershins. Unequaled Christos redecorate compulsively. To select either by establishing pairings of database schema objects structure To visualize a database you never create one explain more diagrams illustrating some or all refer the tables columns keys and relationships in manual For any couple you have create as many database diagrams as strong like this database vault can guard on any process of diagrams. Entity Data Modeling with Visual Studio James Serra's Blog. Entity Relationship Diagrams ERDs Lucidchart. SchemaSpy. SQL Server Database Diagram Tool in Management Studio. How know you diagram a SQL database? SQL Server How to export Database Diagram to Excel. Documentation script Introducing schema documentation in SQL Server. Diagrams Data model definition Define data model manually with YAML Extract data model from R data frames Reverse-engineer SQL Server Database. Tables are the brown primary building blocks of a database A Table is very much house a pit table or spreadsheet containing rows records arranged in different columns fields At the intersection of notice and outside row cost the individual bit of fair for easy particular record called a cell. Display views in database diagram SQLServerCentral. Above is follow simple example saw a schema diagram It shows three tables along with primitive data types relationships between the tables as specific as there primary keys and foreign keys. In this ER Diagram view log can become table fields and relationships between tables in data database andor schema graphically It also allows adding foreign key.
    [Show full text]
  • The Relational Model
    The Relational Model Read Text Chapter 3 Laks VS Lakshmanan; Based on Ramakrishnan & Gehrke, DB Management Systems Learning Goals given an ER model of an application, design a minimum number of correct tables that capture the information in it given an ER model with inheritance relations, weak entities and aggregations, design the right tables for it given a table design, create correct tables for this design in SQL, including primary and foreign key constraints compare different table designs for the same problem, identify errors and provide corrections Unit 3 2 Historical Perspective Introduced by Edgar Codd (IBM) in 1970 Most widely used model today. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc. “Legacy systems” are usually hierarchical or network models (i.e., not relational) e.g., IMS, IDMS, … Unit 3 3 Historical Perspective Competitor: object-oriented model ObjectStore, Versant, Ontos A synthesis emerging: object-relational model o Informix Universal Server, UniSQL, O2, Oracle, DB2 Recent competitor: XML data model In all cases, relational systems have been extended to support additional features, e.g., objects, XML, text, images, … Unit 3 4 Main Characteristics of the Relational Model Exceedingly simple to understand All kinds of data abstracted and represented as a table Simple query language separate from application language Lots of bells and whistles to do complicated things Unit 3 5 Structure of Relational Databases Relational database: a set of relations Relation: made up of 2 parts: Schema : specifies name of relation, plus name and domain (type) of each field (or column or attribute). o e.g., Student (sid: string, name: string, address: string, phone: string, major: string).
    [Show full text]
  • Relational Database Manipulation Basic Relational Database Query
    Basic Relational Database Query Operations • Three basic relational database query operations: Relational Database – Projection: retrieve selected attributes from a relation Manipulation – Selection (Restriction): retrieve selected tuples from a relation – Join: combine two or more relations Robert C. Nickerson • Note: All relational database query operations ISYS 464 – Spring 2003 take one or more relations as input and produce Topic 08 one relation as output Copyright (c) 2003 by All rights reserved. 1 Copyright (c) 2003 by All rights reserved. 2 Robert C. Nickerson Not for general distribution. Robert C. Nickerson Not for general distribution. Student Course Database Basic Relational Database Student (Student Number, Student Name, Major) Course (Course Number, Course Name, Day, Time) Update Operations Student Course (Student Number, Course Number) Student • Three basic relational database update operations: Student Student Major Student Course Number Name Student Course – Add: insert one or more new tuples in a relation 123 Joe IS Number Number 234 Fred IS 123 ISYS 365 – Delete: remove one or more existing tuples from a 345 Mary Acct 123 FIN 350 relation 456 Sue Mgmt 123 MGMT 405 567 Lee Acct 234 ISYS 365 – Change: modify certain data in one or more tuples of a Course 234 FIN 350 Course Course Name Day Time 234 MGMT 405 relation Number 234 MKTG 431 ISYS 365 Adv C++ MW 12:30 345 ISYS 464 • Note: All relational database update operations ISYS 464 Database TTh 9:30 567 ISYS 464 ISYS 565 Data Comm TTh 14:00 567 ISYS 565 take one relation as input and produce a modified IBUS 330 Int Business MW 8:00 567 MGMT 405 FIN 350 Finance MW 14:00 678 ISYS 363 form of that relation as output MGMT 405 Org Behavior MW 15:30 678 MGMT 405 MKTG 431 Marketing TTh 8:00 Copyright (c) 2003 by All rights reserved.
    [Show full text]