11. Table Operations – Implementation

Total Page:16

File Type:pdf, Size:1020Kb

11. Table Operations – Implementation Realization of DBS 11. Table Operations – Implementation Theo Härder www.haerder.de Goals - Systematic development of relational processing concepts for a single table or for several tables - Realization of plan operators Main reference: Theo Härder, Erhard Rahm: Datenbanksysteme – Konzepte und Techniken der Implementierung, Springer, 2001, Chapter 11. Goetz Graefe: Query Evaluation Techniques for Large Databases, ACM Computing Surveys 25:2, June 1993, pp. 73-170. Realization of Database Systems – SS 2011 © 2011 AG DBIS Realization of DBS Table Operations - Implementation Operations of the relational algebra - Unary operations: , Table Sort operations - Binary operations: , , , , , – Plan operators R T S Nested-loops & sort/merge join SQL queries contain logical expressions which can be mapped to the operations of the relational algebra. They are further transformed into Hash join access plans. So-called plan operators implement these logical operations Joins on type- Plan operators on a single table spanning paths Selection Distributed joins Operators across several tables Set operations Join algorithms - Nested-loops join, Sort-merge join - Hash join (classic hashing, simple hash join, hybrid hash join) - Exploitation of type-crossing access paths - Distributed join algorithms Further binary operations (set operations) © 2011 AG DBIS 11-2 Realization of DBS Plan Operators on a Single Table Selection – general ways of evaluation Table • Direct access via a given TID, via a hash method or a one- resp. multi- operations dimensional index structure • Sequential search in a table Plan operators • Search via an index structure (index table, bitlist) • Selection using several pointer lists where more than a single index Nested-loops & sort/merge join structure can be exploited • Search via a multi-dimensional index structure Hash join Joins on type- Projection spanning paths is typically performed in combination with sorting, selection, or join Distributed joins Modification Set operations • Updates are set-oriented in SQL, but restricted to a single table • INSERT, DELETE and UPDATE are directly mapped to the corresponding operations of the storage structures • “Automatic” execution of maintenance operations - to update access paths, - to guarantee clustering and reorganization etc. • Provisions for logging and recovery etc. © 2011 AG DBIS 11-3 Realization of DBS Plan Operators for the Selection Use of Scan Operators • Definition of start- and stop condition Table • Definition of simple search arguments operations Plan operators Plan operators 1. Table scan (relation scan) - Always possible Nested-loops & sort/merge join - SCAN operator implements selection operation 2. Index scan Hash join - Selection of most cost-effective index - Specification of search range (start-, stop condition) Joins on type- 3. k-d scan spanning paths - Evaluation of multi-dimensional search criteria - Use of differing evaluation directions by navigation Distributed joins 4. TID algorithm - Evaluation of all “useable" index structures Set operations - Location of TID lists of variable lengths - Boolean connection of the lists - Access to the records according to the hit list (result list) Further plan operators in combination with selection • Sorting • Grouping (see sort operator) • Special operators e.g. in Data-Warehouse applications for grouping and © 2011 AG DBIS aggregation (CUBE operator) 11-4 Realization of DBS Operators Across Several Tables SQL allows complex queries across k tables • One-variable expressions: Table describe conditions for the selection of elements from a table operations • Two-variable expressions: describe conditions for the combination of elements from two tables Plan operators • Typically, k-variable expressions are decomposed into one- and two-variable expressidltdbdiltions and evaluated by corresponding plan operators Nested-loops & sort/merge join Plan operators across several tables Hash join • General ways for the evaluation: - Nested iteration Joins on type- for each element of outer table T spanning paths o traversal of inner table Ti • O(No · Ni + No) Distributed joins • important application: nested-loops join - Merge method Set operations iterating traversals through T1, T2 • O(N1 + N2) • additional sort costs, if necessary • important application: merging join - Hashing Partitioning of inner table Ti and partition-wise loading in HT in memory. “Probing” by outer table To or its © 2011 AG DBIS resp. partitions using HT: O(p · No + Ni) 11-5 Realization of DBS Operators Across Several Tables (2) n-way joins • Decomposition into n-1 two-way joins2 Table operations • Number of possible join sequences is dependent on the join attributes chosen • Maximal n! different sequences possible Plan operators • Use of pipelining techniques • OiOptimal eval uati on sequence d epend ent on Nested-loops & sort/merge join - Plan operators - “Fitting” sort orders for join attributes Hash join - Size of operands etc. Joins on type- Some join sequences using two-way joins (n=5) spanning paths result result Distributed joins result Set operations T5 T2 T4 T5 T4 T3 T5 T1 T2 T1 T2 T3 T4 T3 T1 left-deep tree bushy tree right-deep tree Analogous proceeding in case of set operations © 2011 AG DBIS 2. Practicality test (Guy Lohman test for join techniques): Does a new technique apply to joining three inputs without 11-6 interrupting data flow between the join operators? Realization of DBS Plan Operators for the Join Join • Record-type-spanning operation: usually very expensive Table • Frequent use: important optimization candidate operations • Typical application: equi-join • General Θ-join infrequent Plan operators Imppjplementation of the join operation can process, at the same time, selections (and projections) on the participating tables R and S Nested-loops & sort/merge join SELECT * FROM R, S Hash join WHERE R.JA Θ S.JA AND PR AND P Joins on type- S spanning paths • JA: join attribute • PR and PS: predicates defined on selection attributes (SA) of R and S Distributed joins Possible access paths Set operations • Scans over R and S (always) • Scans over IR(JA), IS(JA) (if present) deliver sort sequence according to JA • Scans over IR(SA), IS(SA) (if present) if necessary, fast selection for PR and PS • Scans over other index structures (if present) if necessary, faster location of all records © 2011 AG DBIS 11-7 Realization of DBS Nested-Loops Join Assumptions • Records in R and S are not ordered according to join attributes Table • Index structures IR(JA) and IS(JA) do not exist operations Algorithm for Θ-join Scan over S, Plan operators for each record s, if PS: scan over R, Nested-loops & for each record r, if PR AND (r.JA Θ s.JA): sort/merge join execute join, i.e., write combined record (r, s) into the result set. Hash join Complexity: O(N*M) Joins on type- Nested-loops join using index access spanning paths Scan over S, for each record s, if PS: determine via access to IR(JA) all TIDs for records satisfying r.JA = s.JA, Distributed joins for each TID: fetch record r, if PR: write combdbined recor d()d (r, s ) into th e resul t set. Set operations Nested-block join Scan over S, for each page (resp. set of contiguous pages) of S: scan over R, for each page (resp. set of contiguous pages) of R: for each record s of the S-page, if PS: for each record r of the R-page, if PR AND (r.JA Θ s.JA): write combined record (r, s) into the result set. © 2011 AG DBIS 11-8 Realization of DBS Sort-Merge Join Algorithm consists of 2 phases • Phase 1: Sorting of R and S w.r.t R(JA) and S(JA) (if not already present); Table in doing so, early elimination of records not needed ( P , P ) operations R S • Phase 2: Iterating scans over sorted R- and S-records Plan operators where join is performed in case of r.JA = s.JA Complexity: O(N log N) Nested-loops & sort/merge join Special case Hash join If either IR(JA) and IS(JA) or GAPS over R(JA) and S(JA) (join index) is present: exploitation of index structures on join attributes Joins on type- Iterating scans over I (JA) and I (JA): spanning paths R S for each with two keys from IR(JA) and IS(JA), if r.JA = s.JA: fetch the records using the related TIDs, Distributed joins if PR and PS: write combined record (r , s) into the result set Set operations © 2011 AG DBIS 11-9 Realization of DBS Hash Join Simplest case (classic hashing) • Step 1: Partitioned read of (smaller) table R and construction of a hash Table operations table using hH(r(JA)) w.r.t. values of R(JA) of partitions Ri (1 i p): each partition fits into the available memory and each record satisfies PR Plan operators • Step 2: Probing for records of S using PS; if successful, execution of join Nested-loops & • Step 3: Repeat steps 1 and 2 as long as R is exhausted sort/merge join Construction of hash tables and probing Hash join Scan over R; building hash tables Hi (1 i p) one at a time in memory Joins on type- H spanning paths R 1 Scan over S with probing of S Distributed joins H1 . Set operations H R p Scan over S with probing of S HP Complexity: O(p · N) Special case R fits into memory: one partition (p = 1) 11-10 © 2011 AG DBIS a single scan over S is sufficient! Realization of DBS Hash Join (2) Partitioning of R with hp(r(JA)) Table operations #records / JA-value Plan operators Nested-loops & sort/merge join JA 0 100 Hash join #records / JA’-value hp(r(JA)) Joins on type- spanning paths JA’ Distributed joins 0 0.33 0.66 1 R R R Set operations 1 2 3 © 2011 AG DBIS 11-11 Realization of DBS Hash Join (3) Partitioning Table • Partitioning of R in subsets R1, R2, ..., Rp: operations a record r of R is in Ri, if h(r) is in Hi Plan operators R Nested-loops & sort/merge join Hash join Joins on type- .
Recommended publications
  • Chapter 11 Querying
    Oracle TIGHT / Oracle Database 11g & MySQL 5.6 Developer Handbook / Michael McLaughlin / 885-8 Blind folio: 273 CHAPTER 11 Querying 273 11-ch11.indd 273 9/5/11 4:23:56 PM Oracle TIGHT / Oracle Database 11g & MySQL 5.6 Developer Handbook / Michael McLaughlin / 885-8 Oracle TIGHT / Oracle Database 11g & MySQL 5.6 Developer Handbook / Michael McLaughlin / 885-8 274 Oracle Database 11g & MySQL 5.6 Developer Handbook Chapter 11: Querying 275 he SQL SELECT statement lets you query data from the database. In many of the previous chapters, you’ve seen examples of queries. Queries support several different types of subqueries, such as nested queries that run independently or T correlated nested queries. Correlated nested queries run with a dependency on the outer or containing query. This chapter shows you how to work with column returns from queries and how to join tables into multiple table result sets. Result sets are like tables because they’re two-dimensional data sets. The data sets can be a subset of one table or a set of values from two or more tables. The SELECT list determines what’s returned from a query into a result set. The SELECT list is the set of columns and expressions returned by a SELECT statement. The SELECT list defines the record structure of the result set, which is the result set’s first dimension. The number of rows returned from the query defines the elements of a record structure list, which is the result set’s second dimension. You filter single tables to get subsets of a table, and you join tables into a larger result set to get a superset of any one table by returning a result set of the join between two or more tables.
    [Show full text]
  • Using the Set Operators Questions
    UUSSIINNGG TTHHEE SSEETT OOPPEERRAATTOORRSS QQUUEESSTTIIOONNSS http://www.tutorialspoint.com/sql_certificate/using_the_set_operators_questions.htm Copyright © tutorialspoint.com 1.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: A. Set operators are used to combine the results of two ormore SELECT statements.Valid set operators in Oracle 11g are UNION, UNION ALL, INTERSECT, and MINUS. When used with two SELECT statements, the UNION set operator returns the results of both queries.However,if there are any duplicates, they are removed, and the duplicated record is listed only once.To include duplicates in the results,use the UNION ALL set operator.INTERSECT lists only records that are returned by both queries; the MINUS set operator removes the second query's results from the output if they are also found in the first query's results. INTERSECT and MINUS set operations produce unduplicated results. 2.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: B. UNION ALL Returns the combined rows from two queries without sorting or removing duplicates. sql_certificate 3.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: C. INTERSECT Returns only the rows that occur in both queries' result sets, sorting them and removing duplicates. 4.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: D. MINUS Returns only the rows in the first result set that do not appear in the second result set, sorting them and removing duplicates.
    [Show full text]
  • SQL Version Analysis
    Rory McGann SQL Version Analysis Structured Query Language, or SQL, is a powerful tool for interacting with and utilizing databases through the use of relational algebra and calculus, allowing for efficient and effective manipulation and analysis of data within databases. There have been many revisions of SQL, some minor and others major, since its standardization by ANSI in 1986, and in this paper I will discuss several of the changes that led to improved usefulness of the language. In 1970, Dr. E. F. Codd published a paper in the Association of Computer Machinery titled A Relational Model of Data for Large shared Data Banks, which detailed a model for Relational database Management systems (RDBMS) [1]. In order to make use of this model, a language was needed to manage the data stored in these RDBMSs. In the early 1970’s SQL was developed by Donald Chamberlin and Raymond Boyce at IBM, accomplishing this goal. In 1986 SQL was standardized by the American National Standards Institute as SQL-86 and also by The International Organization for Standardization in 1987. The structure of SQL-86 was largely similar to SQL as we know it today with functionality being implemented though Data Manipulation Language (DML), which defines verbs such as select, insert into, update, and delete that are used to query or change the contents of a database. SQL-86 defined two ways to process a DML, direct processing where actual SQL commands are used, and embedded SQL where SQL statements are embedded within programs written in other languages. SQL-86 supported Cobol, Fortran, Pascal and PL/1.
    [Show full text]
  • “A Relational Model of Data for Large Shared Data Banks”
    “A RELATIONAL MODEL OF DATA FOR LARGE SHARED DATA BANKS” Through the internet, I find more information about Edgar F. Codd. He is a mathematician and computer scientist who laid the theoretical foundation for relational databases--the standard method by which information is organized in and retrieved from computers. In 1981, he received the A. M. Turing Award, the highest honor in the computer science field for his fundamental and continuing contributions to the theory and practice of database management systems. This paper is concerned with the application of elementary relation theory to systems which provide shared access to large banks of formatted data. It is divided into two sections. In section 1, a relational model of data is proposed as a basis for protecting users of formatted data systems from the potentially disruptive changes in data representation caused by growth in the data bank and changes in traffic. A normal form for the time-varying collection of relationships is introduced. In Section 2, certain operations on relations are discussed and applied to the problems of redundancy and consistency in the user's model. Relational model provides a means of describing data with its natural structure only--that is, without superimposing any additional structure for machine representation purposes. Accordingly, it provides a basis for a high level data language which will yield maximal independence between programs on the one hand and machine representation and organization of data on the other. A further advantage of the relational view is that it forms a sound basis for treating derivability, redundancy, and consistency of relations.
    [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]
  • Best Practices Managing XML Data
    ® IBM® DB2® for Linux®, UNIX®, and Windows® Best Practices Managing XML Data Matthias Nicola IBM Silicon Valley Lab Susanne Englert IBM Silicon Valley Lab Last updated: January 2011 Managing XML Data Page 2 Executive summary ............................................................................................. 4 Why XML .............................................................................................................. 5 Pros and cons of XML and relational data ................................................. 5 XML solutions to relational data model problems.................................... 6 Benefits of DB2 pureXML over alternative storage options .................... 8 Best practices for DB2 pureXML: Overview .................................................. 10 Sample scenario: derivative trades in FpML format............................... 11 Sample data and tables................................................................................ 11 Choosing the right storage options for XML data......................................... 16 Selecting table space type and page size for XML data.......................... 16 Different table spaces and page size for XML and relational data ....... 16 Inlining and compression of XML data .................................................... 17 Guidelines for adding XML data to a DB2 database .................................... 20 Inserting XML documents with high performance ................................ 20 Splitting large XML documents into smaller pieces ..............................
    [Show full text]
  • Chapter 2 – Object-Relational Views and Composite Types Outline
    Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 [email protected] Chapter 2 – Object-Relational Views and Composite Types Recent Developments for Data Models Outline Overview I. Object-Relational Database Concepts 1. User-defined Data Types and Typed Tables 2. Object-relational Views and Composite Types 3. User-defined Routines and Object Behavior 4. Application Programs and Object-relational Capabilities 5. Object-relational SQL and Java II. Online Analytic Processing 6. Data Analysis in SQL 7. Windows and Query Functions in SQL III. XML 8. XML and Databases 9. SQL/XML 10. XQuery IV. More Developments (if there is time left) temporal data models, data streams, databases and uncertainty, … 2 © Prof.Dr.-Ing. Stefan Deßloch Recent Developments for Data Models 1 The "Big Picture" Client DB Server Server-side dynamic SQL Logic SQL99/2003 JDBC 2.0 SQL92 static SQL SQL OLB stored procedures ANSI SQLJ Part 1 user-defined functions SQL Routines ISO advanced datatypes PSM structured types External Routines subtyping methods SQLJ Part 2 3 © Prof.Dr.-Ing. Stefan Deßloch Recent Developments for Data Models Objects Meet Databases (Atkinson et. al.) Object-oriented features to be supported by an (OO)DBMS ; Extensibility user-defined types (structure and operations) as first class citizens strengthens some capabilities defined above (encapsulation, types) ; Object identity object exists independent of its value (i.e., identical ≠ equal) ; Types and classes "abstract data types", static type checking class as an "object factory", extension (i.e., set of "instances") ? Type or class and view hierarchies inheritance, specialization ? Complex objects type constructors: tuple, set, list, array, … Encapsulation separate specification (interface) from implementation Overloading, overriding, late binding same name for different operations or implementations Computational completeness use DML to express any computable function (-> method implementation) 4 © Prof.Dr.-Ing.
    [Show full text]
  • On the Logic of SQL Nulls
    On the Logic of SQL Nulls Enrico Franconi and Sergio Tessaris Free University of Bozen-Bolzano, Italy lastname @inf.unibz.it Abstract The logic of nulls in databases has been subject of invest- igation since their introduction in Codd's Relational Model, which is the foundation of the SQL standard. In the logic based approaches to modelling relational databases proposed so far, nulls are considered as representing unknown values. Such existential semantics fails to capture the behaviour of the SQL standard. We show that, according to Codd's Relational Model, a SQL null value represents a non-existing value; as a consequence no indeterminacy is introduced by SQL null values. In this paper we introduce an extension of first-order logic accounting for predicates with missing arguments. We show that the domain inde- pendent fragment of this logic is equivalent to Codd's relational algebra with SQL nulls. Moreover, we prove a faithful encoding of the logic into standard first-order logic, so that we can employ classical deduction ma- chinery. 1 Relational Databases and SQL Null Values Consider a database instance with null values over the relational schema fR=2g, and a SQL query asking for the tuples in R being equal to themselves: 1 2 1 | 2 SELECT * FROM R ---+--- R : a b WHERE R.1 = R.1 AND R.2 = R.2 ; ) a | b b N (1 row) Figure 1. In SQL, the query above returns the table R if and only if the table R does not have any null value, otherwise it returns just the tuples not containing a null value, i.e., in this case only the first tuple ha; bi.
    [Show full text]
  • Information Technology — Database Languages — SQL — Part 14: XML
    WG3:SIA-010 H2-2003-427 ISO/IEC JTC 1/SC 32 Date: 2003-12-29 WD ISO/IEC 9075-14:2007 (E) ISO/IEC JTC 1/SC 32/WG 3 United States of America (ANSI) Information technology Ð Database languages Ð SQL Ð Part 14: XML-Related Specifications (SQL/XML) Technologies de l©informationÐ Langages de base de données — SQL — Partie 14: Specifications à XML (SQL/XML) Document type: International Standard Document subtype: Working Draft (WD) Document stage: (2) WD under Consideration Document language: English PDF rendering performed by XEP, courtesy of RenderX, Inc. Copyright notice This ISO document is a working draft or a committee draft and is copyright-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO. Requests for permission to reproduce for the purpose of selling it should be addressed as shown below or to ISO©s member body in the country of the requester. ANSI Customer Service Department 25 West 43rd Street, 4th Floor New York, NY 10036 Tele: 1-212-642-4980 Fax: 1-212-302-1286 Email: [email protected] Web: www.ansi.org Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violaters may be prosecuted. Contents Page Foreword. ix Introduction. x 1 Scope. 1 2 Normative references.
    [Show full text]
  • DS 1300 - Introduction to SQL Part 3 – Aggregation & Other Topics
    DS 1300 - Introduction to SQL Part 3 – Aggregation & other Topics by Michael Hahsler Based on slides for CS145 Introduction to Databases (Stanford) Lecture Overview 1. Aggregation & GROUP BY 2. Advanced SQL-izing (set operations, NULL, Outer Joins, etc.) 2 AGGREGATION, GROUP BY AND HAVING CLAUSE 3 Aggregation SELECT COUNT(*) SELECT AVG(price) FROM Product FROM Product WHERE year > 1995 WHERE maker = ‘Toyota’ • SQL supports several aggregation operations: • SUM, COUNT, MIN, MAX, AVG Except for COUNT, all aggregations apply to a single attribute! 4 Aggregation: COUNT COUNT counts the number of tuples including duplicates. SELECT COUNT(category) Note: Same as FROM Product COUNT(*)! WHERE year > 1995 We probably want count the number of “different” categories: SELECT COUNT(DISTINCT category) FROM Product WHERE year > 1995 5 More Examples Purchase(product, date, price, quantity) SELECT SUM(price * quantity) FROM Purchase What do these mean? SELECT SUM(price * quantity) FROM Purchase WHERE product = ‘bagel’ 6 Simple Aggregations Purchase Product Date Price Quantity bagel 10/21 1 20 banana 10/3 0.5 10 banana 10/10 1 10 bagel 10/25 1.50 20 SELECT SUM(price * quantity) FROM Purchase 50 (= 1*20 + 1.50*20) WHERE product = ‘bagel’ 7 Grouping and Aggregation Purchase(product, date, price, quantity) Find total sales after Oct 1, 2010, SELECT product, per product. SUM(price * quantity) AS TotalSales FROM Purchase Note: Be very careful WHERE date > ‘2000-10-01’ with dates! GROUP BY product Use date/time related Let’s see what this means… functions! 8 Grouping and Aggregation Semantics of the query: 1. Compute the FROM and WHERE clauses 2.
    [Show full text]
  • Relational Completeness of Data Base Sublanguages
    RELATIONAL COMPLETENESS OF DATA BASE SUBLANGUAGES E. F. Codd IBM Research Laboratory San Jose, California ABSTRACT: In the near future, we can expect a great variety of languages to be proposed for interrogating and updating data bases. This paper attempts to provide a theoretical basis which may be used to determine how complete a selection capability is provided in a proposed data sublanguage independently of any host language in which the sublanguage may be embedded. A relational algebra and a relational calculus are defined. Then, an algorithm is presented for reducing an arbitrary relation-defining expression (based on the calculus) into a semantically equivalent expression of the relational algebra. Finally, some opinions are stated regarding the relative merits of calculus- oriented versus algebra-oriented data sublanguages from the standpoint of optimal search and highly discriminating authorization schemes. RJ 987 Hl7041) March 6, 1972 Computer Sciences 1 1. INTRODUCTION In the near future we can expect a great variety of languages to be proposed for interrogating and updating data bases. When the computation- oriented components of such a language are removed, we refer to the remaining storage and retrieval oriented sublanguage as a data sublanguaqe. A data sublanguage may be embedded in a general purpose programming language, or it may be stand-alone -- in which case, it is commonly called a query language (even though it may contain provision for simple updating as well as querying). This paper attempts to establish a theoretical basis which may be used to determine how complete a selection capability is provided in a proposed data sublanguage independently of any host language in which the sublanguage may be embedded.
    [Show full text]
  • A Next Generation Data Language Proposal
    A Next Generation Data Language Proposal Eugene Panferov Independent researcher, 11A Milosava Djorica, 11427 Vranic, Barajevo, Serbia Abstract This paper analyzes the fatal drawback of the relational calculus not allowing relations to be domains of relations, and its consequences entrenched in SQL. In order to overcome this obstacle we propose multitable index – an easily implementable upgrade to an existing data storage, which enables a revolutionary change in the field of data languages – the demotion of relational calculus and “tables”. We propose a new data language with pragmatic typisation where types represent domain knowledge but not memory management. The language handles sets of tuples as first class data objects and supports set operation and tuple (de)composition operations as fluently basic arith. And it is equally suitable for building-into a general purpose language as well as querying a remote DB (thus removing the ubiquitous gap between SQL and “application”). Keywords pragmatic typisation, data language, multitable index 1. Introduction In the year 1972 Edgar. F. Codd stated his anticipation as follows: In the near future, we can expect a great variety of languages to be proposed for interrogating and updating data bases. It is now 2021. The only data language of any significance is SQL. Something clearly has gone wrong? We attempt to analyze what aspects of SQL are holding back any development in the area of data languages, and propose radical solutions in both abstraction layers: data language and data storage. Back in 1970s data languages were seen as sub-languages of general-purpose languages [2]. Instead something very opposite has grown – a complete perfect isolation of general purpose languages from the database interrogation language – splitting every program in two poorly interacting parts.
    [Show full text]