TL;DR: SQL for Smarties as discussed by the authors was the first book devoted explicitly to the advanced techniques needed to transform an experienced SQL programmer into an expert, and it is the only book written by a SQL master that teaches programmers and practitioners to become SQL masters themselves.
Abstract: SQL for Smarties was hailed as the first book devoted explicitly to the advanced techniques needed to transform an experienced SQL programmer into an expert. Now, 20 years later and in its fifth edition, this classic reference still reigns supreme as the only book written by a SQL master that teaches programmers and practitioners to become SQL masters themselves! These are not just tips and techniques; also offered are the best solutions to old and new challenges. Joe Celko conveys the way you need to think in order to get the most out of SQL programming efforts for both correctness and performance. New to the fifth edition, Joe features new examples to reflect the ANSI/ISO Standards so anyone can use it. He also updates data element names to meet new ISO-11179 rules with the same experience-based teaching style that made the previous editions the classics they are today. You will learn new ways to write common queries, such as finding coverings, partitions, runs in data, auctions and inventory, relational divisions and so forth. SQL for Smarties explains some of the principles of SQL programming as well as the code. A new chapter discusses design flaws in DDL, such as attribute splitting, non-normal forum redundancies and tibbling. There is a look at the traditional acid versus base transaction models, now popular in NoSQL products. Youll learn about computed columns and the DEFERRABLE options in constraints. An overview of the bi-temporal model is new to this edition and there is a longer discussion about descriptive statistic aggregate functions. The book finishes with an overview of SQL/PSM that is applicable to proprietary 4GL vendor extensions.New to the 5th Edition: Downloadable data sets, code samples, and vendor-specific implementations!Overview of the bitemporal modelExtended coverage of descriptive statistic aggregate functionsNew chapter covers flaws in DDLExamination of traditional acid versus base transaction modelsReorganized to help you navigate related topics with easeExpert advice from a noted SQL authority and award-winning columnist Joe Celko, who served on the ANSI SQL standards committee for over a decadeTeaches scores of advanced techniques that can be used with any product, in any SQL environment, whether it is SQL 92 or SQL 2011 Offers tips for working around deficiencies and gives insight into real-world challenges
TL;DR: This article examines the creation and manipulation of temporal data using built-in temporal logic and compares its performance with the performance of equivalent hand-coded applications.
Abstract: Recently, the ANSI committee for the standardization of the SQL language has published the specification for temporal data support. This new ability allows users to create and manipulate temporal data in a significantly simpler way instead of implementing the same features using triggers and database applications. In this article we examine the creation and manipulation of temporal data using built-in temporal logic and compare its performance with the performance of equivalent hand-coded applications. For this study, we use an existing commercial database system, which supports the standardized temporal data model.
TL;DR: An interval-based temporal query language (TQL), which is proposed for this task, is defined via naturally characterizable combinations of temporal logic with conjunctive queries, which warrants well-defined semantics and formal properties of TQL querying.
Abstract: We develop a practical approach to querying temporal data stored in temporal SQL:2011 databases through the semantic layer of OWL 2 QL ontologies. An interval-based temporal query language (TQL), which we propose for this task, is defined via naturally characterizable combinations of temporal logic with conjunctive queries. This foundation warrants well-defined semantics and formal properties of TQL querying. In particular, we show that under certain mild restrictions the data complexity of query answering remains in AC, i.e., as in the usual, nontemporal case. On the practical side, TQL is tailored specifically to offer maximum expressivity while preserving the possibility of reusing standard first-order rewriting techniques and tools for OWL 2 QL.
TL;DR: In this paper, an AI SQL parser for decision-type distributed database systems is presented. And the parser and method adopt AI SQL as the extension of SQL 2011 specification, which reduces the compilation, packaging, deployment links, testing work is simpler, thus reducing the AI analysis project personnel costs and implementation cycle.
Abstract: The invention belongs to an SQL parser supporting AI SQL, in particular to an AI SQL parser in a decision-type distributed database system and an implementation method thereof The present invention provides a new AI SQL parser in decision-type distributed database system and an implementation method thereof, The parser and method adopt AI SQL as the extension of SQL 2011 specification, Compared with the secondary development of AI analysis program, Because of the inherent declarative nature of the SQL language, AI SQL much is easier to master and use than other AI programmers such as Python/Java/C/C + +, so that the AI SQL can be mastered by data analysts who are generally proficient in SQL, without the need for additional AI programmers proficient in Python/Java/C/C + + And AI SQL usesdecision-making data as the execution platform, compared with the re-development process of AI analysis program, it reduces the compilation, packaging, deployment links, testing work is simpler, thusreducing the AI analysis project personnel costs and implementation cycle
TL;DR: In this article, the authors present the ETL process considerations for temporal databases sources and propose a specialized ETL procedure for the case that temporal databases are used as the data sources of data warehouses.
Abstract: Data warehouses are databases which store integrated enterprise-level information from information system data sources across the organization. These data sources may employ different database management systems, use different data formats, and use different value coding standards. Integrated data availability at the enterprise level from such diverse data sources requires transfers from transactional data sources, transforms them to the standard format, and loads them into the data warehouse. This process is known as the Extract Transform Load (ETL) process. At present, temporal databases which support validtime are available and temporal extensions to SQL are standard features since SQL 2011. The challenge is the temporal feature of temporal databases is different from the time dimension of conventional data warehouses. Thus specialized ETL procedures are required in the case that temporal databases are used as the data sources of data warehouses. In this paper, ETL process considerations for temporal databases sources are presented.