Incremental updates for materialized OQL views

Gluche, Dieter; Grust, Torsten; Mainberger, Christof; Scholl, Marc H.

doi:10.1007/3-540-63792-3_8

Cited by 23 publications

(23 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…, 4,12,14,18,21,22,23,25,26,29,30,33]; this is due to the still lacking agreement on standardization in the field. Complex structures (nesting) commonality between object-oriented and the nested relational models icad to having an object-oriented view maintenance approach applicable to the nested relational model ,~nd hence to the conventional relational model, However, the inheritance and hence reusability distinguishing feature of object-oriented models makes view maintenance within the object-oriented context unique, i.e., no approach developed for the relational model remains applicable to the ,.~bject-oriented level.…”

Section: I1mentioning

confidence: 99%

See 1 more Smart Citation

Incremental materialization of object-oriented views

Alhajj

Elnagar

1999

Data & Knowledge Engineering

View full text Add to dashboard Cite

We present an approach to handle incremental materialization of object-oriented views. Queries that define views are implemented as methods that are invoked to compute corresponding views. To avoid computation from scratch each time a view is accessed, we introduce some deferred update algorithms that reflect for a view only related modifications introduced into the database while that view was inactive. A view is updated by considering modifications performed within all classes along the inheritance and class-composition subhierarchies rooted at every class used in deriving that view. To each class, we add a modification list to keep one modification tuple per view dependent on that class. Such a tuple acts as a reference point that marks the start of the next update to the corresponding view.

show abstract

Section: I1mentioning

confidence: 99%

“…This allows update resolution to be implemented in a consistent way. The CROQUE approach to the maintenance of materialized views is discussed in [18], where views are treated as functions of database objects. The algebraic properties of those functions were examined to derive incremental update plans.…”

Section: Related Workmentioning

confidence: 99%

Incremental materialization of object-oriented views

Alhajj

Elnagar

1999

Data & Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…The importance of the idempotence property for update optimization for the task of incremental maintenance of materialized views [4], has been identified in [3]. More recently, idempotent operations have been found useful also in a broader setting in the area of distributed systems [2,6].…”

Section: Introductionmentioning

confidence: 99%

Loop Elimination for Database Updates

Savenkov

Pichler

2013

Big Data

View full text Add to dashboard Cite

Abstract. The additional expressive power of procedural extensions of query and update languages come at the expense of trading the efficient set-at-a-time processing of database engines for the much less efficient tuple-at-a-time processing of a procedural language. In this work, we consider the problem of rewriting for-loops with update statements into sequences of updates which do not use loops or cursors and which simultaneously carry out the action of several loop iterations in a set-at-a-time manner. We identify idempotence as the crucial condition for allowing such a rewriting. We formulate concrete rewrite rules for single updates in a loop and extend them to sequences of updates in a loop.

show abstract

“…Compared to the fully vertical fragmentation, another pattern is the partial vertical fragmentation (Gluche, Grust, Mainberger, & Scholl, 1997). It assumes the prior knowledge of which columns are frequently accessed together.…”

Section: Customer(id Name Balance) Primary Key: Idmentioning

confidence: 99%

An Asynchronous Method for Write Optimization of Column-Store Databases in Map-Reduce

Feng¹,

Jones²,

Xiong³

et al. 2015

STBD

View full text Add to dashboard Cite

Column-store databases feature a faster data reading speed compared with traditional row-based databases. However, optimizing write operations in a column-store database is a well-known challenge. Most existing works on write performance optimization focus on main-memory column-store databases. In this work, we extend the research on column-store databases in the Map-Reduce environment. We propose a data storage format called Timestamped Binary Association Table (or TBAT) without the need of global indexing. Based on TBAT, a new update method, called Asynchronous Map-Only Update (or AMO Update), is designed to replace the traditional update. A significant improvement in speed performance is shown in experiments when comparing the AMO update with the traditional update.

show abstract

Incremental updates for materialized OQL views

Cited by 23 publications

References 8 publications

Incremental materialization of object-oriented views

Incremental materialization of object-oriented views

Loop Elimination for Database Updates

An Asynchronous Method for Write Optimization of Column-Store Databases in Map-Reduce

Contact Info

Product

Resources

About