TL;DR: System/U as mentioned in this paper is a universal relation database system under development at Standford University which uses the language C on UNIX and is intended to test the use of the universal view, in which the entire database is seen as one relation.
Abstract: System/U is a universal relation database system under development at Standford University which uses the language C on UNIX. The system is intended to test the use of the universal view, in which the entire database is seen as one relation. This paper describes the theory behind System/U, in particular the theory of maximal objects and the connection between a set of attributes. We also describe the implementation of the DDL (Data Description Language) and the DML (Data Manipulation Language), and discuss in detail how the DDL finds maximal objects and how the DML determines the connection between the attributes that appear in a query.
TL;DR: The universal-relation model is introduced, and its fundamental ideas are outlined, and one benefit is a simple yet powerful query-language interface.
Abstract: The universal-relation model is introduced, and its fundamental ideas are outlined. This model keeps access-path independence by removing the need for logical navigation among relations. One benefit is a simple yet powerful query-language interface. Two universal-relation database-management systems are discussed that provide good examples of the model: System/U, developed at Stanford University, and FIDL, developed at International Computers Ltd. in Britain. >
TL;DR: This paper shows that the recent approach to quantitative typing systems for programming languages can be extended to pattern matching features, and defines two resource aware type systems, named U and E, for a lambda-calculus equipped with pairs for both patterns and terms.
Abstract: This paper shows that the recent approach to quantitative typing systems for programming languages can be extended to pattern matching features. Indeed, we define two resource aware type systems, named U and E, for a lambda-calculus equipped with pairs for both patterns and terms. Our typing systems borrow some basic ideas from [BKRDR15], which characterises (head) normalisation in a qualitative way, in the sense that typability and normalisation coincide. But in contrast to [BKRDR15], our (static) systems also provides quantitative information about the dynamics of the calculus. Indeed, system U provides upper bounds for the length of normalisation sequences plus the size of their corresponding normal forms, while system E, which can be seen as a refinement of system U, produces exact bounds for each of them. This is achieved by means of a non-idempotent intersection type system equipped with different technical tools. First of all, we use product types to type pairs, instead of the disjoint unions in [BKRDR15], thus avoiding an overlap between "being a pair" and "being duplicable", resulting in an essential tool to reason about quantitativity. Secondly, typing sequents in system E are decorated with tuples of integers, which provide quantitative information about normalisation sequences, notably time (c.f. length) and space (c.f. size). Another key tool of system E is that the type system distinguishes between consuming (contributing to time) and persistent (contributing to space) constructors. Moreover, the time resource information is remarkably refined, because it discriminates between different kinds of reduction steps performed during evaluation, so that beta reduction, substitution and matching steps are counted separately.
TL;DR: In this paper, the system Δu - W u (u) = 0, for u: n → ℝ n, in the form div T = 0 where T is an appropriate stress-energy tensor, and derive certain a priori consequences on the solutions.
Abstract: We rewrite the system Δu - W u (u) = 0, for u: ℝ n → ℝ n , in the form div T = 0, where T is an appropriate stress-energy tensor, and derive certain a priori consequences on the solutions. In particular, we point out some differences between two paradigms: the phase-transition system, with target a finite set of points, and the Ginzburg—Landau system, with target a connected manifold.
TL;DR: In this article, the authors define two resource aware type systems for a lambda-calculus equipped with pairs for both patterns and terms, named U and E, which provide upper bounds for the length of normalisation sequences plus the size of their corresponding normal forms.
Abstract: This paper shows that the recent approach to quantitative typing systems for programming languages can be extended to pattern matching features. Indeed, we define two resource aware type systems, named U and E, for a lambda-calculus equipped with pairs for both patterns and terms. Our typing systems borrow some basic ideas from [BKRDR15], which characterises (head) normalisation in a qualitative way, in the sense that typability and normalisation coincide. But in contrast to [BKRDR15], our (static) systems also provides quantitative information about the dynamics of the calculus. Indeed, system U provides upper bounds for the length of normalisation sequences plus the size of their corresponding normal forms, while system E, which can be seen as a refinement of system U, produces exact bounds for each of them. This is achieved by means of a non-idempotent intersection type system equipped with different technical tools. First of all, we use product types to type pairs, instead of the disjoint unions in [BKRDR15], thus avoiding an overlap between "being a pair" and "being duplicable", resulting in an essential tool to reason about quantitativity. Secondly, typing sequents in system E are decorated with tuples of integers, which provide quantitative information about normalisation sequences, notably time (c.f. length) and space (c.f. size). Another key tool of system E is that the type system distinguishes between consuming (contributing to time) and persistent (contributing to space) constructors. Moreover, the time resource information is remarkably refined, because it discriminates between different kinds of reduction steps performed during evaluation, so that beta reduction, substitution and matching steps are counted separately.