Teniente, E.; Urp'i, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems". 11th Int. Conf. on Data Engineering (ICDE). Taipei (Taiwan), 1995, pp. 173-183.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....into the subgoals. For the extensional predicates, special rules are created that actually implement the hypothetical changes specified by the collected update requests. It should be mentioned that we are planning to improve the hypothetical reasoning by view maintenance techniques (see e.g. [22]) In our running example, a new rule hyp raise sal of rich(L) # P [ hyp raise sal 10(L; P ) hyp rich(L; P ) will be created, because the original update predicate raise sal of rich appears at the second position of a sequential subgoal. Additional rules have to be constructed, e.g. for ....

.... it is necessary to optimize the consistency checks which consume most of the evaluation time (in the standard database examples like the one above) Another possible variation is a reformulation of the definitions for hypothetical predicates to take view maintenance techniques (see e.g. [22]) into account. 6 Related work It was often mentioned that Transaction Logic [5, 6] has significantly inspired our own work. However, although its semantics is logically founded and under some constraints efficiently computable, it has one drawback: the specification of bulk updates by rules is ....

E. Teniente and T. Urp'i. A common framework for classifying and specifying deductive database updating problems. In Proc. Int. Conf. on Data Engineering (ICDE '95), Taipei, Taiwan, pages 173--182, 1995.

....the static semantics and the evaluation of queries is well understood. However, there is no consensus about the appropriate treatment of dynamic behaviour, i.e. the evolution of the database with time. Various methods to incorporate update constructs into logic databases have been proposed, see [TU95] for a comprehensive classification. In this paper we address the explicit construction of (complex) update programs from basic update operations like insert tuple and delete tuple . This is to be distinguished from the problem of view updates which in a sense implicitly define update ....

....avoid recomputation of unchanged parts it is possible to refer to the results of the last committed state and to deal with increments also for the intensional relations. It is necessary to reconsider the rules for hypothetical reasoning by taking view maintenance into account. Teniente and Urp i [TU95] propose a suitable transformation. Acknowledgement The transformation of update programs into conventional deductive database programs has been implemented by Martin Kohrmann as part of his diploma project [Koh96] ....

E. Teniente and T. Urp'i. A common framework for classifying and specifying deductive database updating problems. In Proc. Int. Conf. on Data Engineering (ICDE '95), Taipei, Taiwan, pages 173--182, 1995.

....due to the inclusion of an specific modification operator, the own definition of the method deals with key information of base and derived predicates. Keywords. view updating, integrity constraint maintenance 1 Introduction Several problems may arise when updating a deductive database [18]. A wellknown problem is that of enforcing database consistency. A deductive database is called consistent if it satisfies a set of integrity constraints. When performing an update, deductive database consistency may be violated. That is, the update, together with the current contents of the ....

Teniente, E.; Urp'i, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems". 11th Int. Conf. on Data Engineering (ICDE). Taipei (Taiwan), 1995, pp. 173-183.

.... side IC maintenance Preventing condition T, dP effects Maintaining DB inconsistency activation A more detailed explanation of the upward and the downward interpretations and of the concrete specifications of the above database updating problems in terms of these interpretations can be found in [TU95]. It is worth to mention that upward problems can be combined among them. All of them share a common starting point (a transaction which consists of a set of base fact updates) and aim at the same goal (to define the changes on derived predicates induced by this transaction) The same reasons ....

Teniente, E.; Urpí, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems", Int. Conf. on Data Engineering (ICDE), Taipei (Taiwan), 1995, pp. 173-183.

....updating and view materialization, and condition monitoring [Oli91, UO92, MT93, TO95, PO95] was the common theoretical basis upon which they all were developed. This basis has facilitated their merging into an integrative framework [Oli91, UO92] and their uniform specification and combination [TU95] in terms of this framework. Furthermore, by using these results, we have been able to develop the FOLRE DDBMS prototype, aimed at providing advanced update capabilities and that is implemented on a Sun OS environment, using ECLiPSe [ECL94] both as development environment and as deductive database ....

....given by the left implication, defines changes on derived predicates induced by changes on base predicates. On the other hand, the downward interpretation, given by the right implication, defines changes on base predicates needed to satisfy changes on derived predicates. As shown in [TU95], database updating problems can be specified in terms of these two interpretations. In FOLRE, we have implemented two methods which are able to compute each of these interpretations: the upward method [UO92] computes the upward interpretation and it is able to incrementally handle integrity ....

Teniente, E.; Urpí, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems", 11th Int. Conf. on Data Eng., Taipei (Taiwan), 1995, pp. 173-183.

.... a distinguishing feature of our methods is the common theoretical basis upon which they all were developed, which has facilitated their merging into a integrative framework [Oli91, UO92] for dealing with update problems in deductive databases as well as for their specification and combination [TU95]. Furthermore, by using these results, we have been able to develop the FOLREDDBMS prototype, where FOLRE stands for Facing On towards Logic database Rule Enforcement . This paper is dedicated to the presentation of the integrative framework and of the architecture of our system. FOLRE bears a ....

....induced by an update, for this purpose. These rules are used to integrate the treatment of view updating, materialized view maintenance, integrity checking and integrity maintenance, condition monitoring or predefined transaction generation. Event rules can be interpreted in two different ways [TU95]. Their upward interpretation defines changes on derived predicates induced by changes on base predicates; their downward interpretation defines changes on base predicates needed to satisfy changes on derived predicates. As shown in [TU95] database updating problems can be specified in terms of ....

[Article contains additional citation context not shown here]

Teniente, E.; Urpí, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems", 11th Int. Conf. on Data Eng., Taipei (Taiwan), 1995, pp. 173-183.

....approaches mentioned above. KEYWORDS: deductive database, updating, integrity checking, integrity maintenance 1 1. Introduction Database updating has attracted a lot of research during last years ( Abi88, Win90] In general, several problems may arise when updating a deductive database [TU95]. One of the most important problems is that of enforcing database consistency. A deductive database is called consistent if it satisfies a set of integrity constraints. When performing an update, database consistency may be violated. That is, the update, together with the current content of the ....

Teniente, E.; Urpí, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems", International Conference on Data Engineering (ICDE'95), Taipei, 1995, pp. 173-182.

....we use also this technique for being able to handle in an integrated way the integrity constraints enforcement approaches mentioned above. 1. Introduction Database updating has attracted a lot of research during last years [Abi88] Several problems may arise when updating a deductive database [TU95]. One of the most important problems is that of enforcing database consistency. A deductive database is called consistent if it satisfies a set of integrity constraints. When performing an update, database consistency may be violated. That is, the update, together with the current content of the ....

Teniente, E.; Urpí, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems", International Conference on Data Engineering (ICDE'95), Taipei, 1995, pp. 173-182.

....materialization, and trigger condition monitoring. However, although developed on a common theoretical corpus, so far our own methods do share with previous ones (some of) the isolation critic mentioned above. To begin solving such shortcoming, and already within the premises of the FOLRE project, [TU95] has stated the theoretical basis for the specification and combination of the above problems within an integrated and well founded framework. Evolving from these theoretical results and heterogeneous prototype systems, we are starting the development of the FOLRE DDBMS. For this we are using a ....

....deductive database definition. It allows to verify satisfiability of deductive rules, integrity constraints and conditions to monitor. Our previous work in this field relies on a prototyped method in the related context of deductive conceptuals models validation [CO92] and on the ideas outlined in [TU95] on how to use view updating techniques for dealing with these issues. Given a validated deductive database definition, the Augmented Database Generator automatically derives the corresponding augmented database. That is, it obtains a model that specifies the changes that occur in a transition ....

Teniente, E.; Urpí, T. "A Common Framework for Classifying and Specifying Deductive Database Updating Problems", to appear in the proceedings of the 11th ICDE, Taiwan, 1995. - 18 -

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC