Maintaining views incrementally

Gupta, Ashish; Mumick, Inderpal Singh; Subrahmanian, V. S.

doi:10.1145/170035.170066

Cited by 449 publications

(196 citation statements)

References 14 publications

Supporting

Mentioning

194

Contrasting

Unclassified

Order By: Relevance

“…The Propagation-Filtering algorithm [19] works on each removed fact separately, propagating it through to all rules which depend on it, while also after each step of the propagation performing a query for alternative support which would end the propagation. In contrast, the Delete-Rederive (DRed) algorithm [18] is rule-oriented and works on sets of facts, first over-approximating all possible deletions that may result from a change in base facts, then re-deriving any still-supported facts from the over-deleted state before finally continuing semi-naive materialization on newly added facts.…”

Section: Incremental Verificationmentioning

confidence: 99%

Efficient verification of railway infrastructure designs against standard regulations

Luteberget

Johansen

2017

Form Methods Syst Des

View full text Add to dashboard Cite

In designing safety-critical infrastructures s.a. railway systems, engineers often have to deal with complex and large-scale designs. Formal methods can play an important role in helping automate various tasks. For railway designs formal methods have mainly been used to verify the safety of so-called interlockings through model checking, which deals with state change and rather complex properties, usually incurring considerable computational burden (e.g., the state-space explosion problem). In contrast, we focus on static infrastructure models, and are interested in checking requirements coming from design guidelines and regulations, as usually given by railway authorities or safety certification bodies. Our goal is to automate the tedious manual work that railway engineers do when ensuring compliance with regulations, through using software that is fast enough to do verification on-the-fly, thus being able to be included in the railway design tools, much like a compiler in an IDE. In consequence, this paper describes the integration into the railway design process of formal methods for automatically extracting railway models from the CAD railway designs and for describing relevant technical regulations and expert knowledge as properties to be checked on the models. We employ a variant of Datalog and use the standardized "railway markup language" railML as basis and exchange format for the formalization. We developed a prototype tool and integrated it in industrial railway CAD software, developed under the name RailCOMPLETE . This on-the-fly verification tool is a help for the engineer while doing the designs, and is not a replacement to other more heavy-weight software like for doing interlocking verification or capacity analysis. Our tool, through the export into railML, can be easily integrated with these other tools. We apply our tool chain in a Norwegian railway project, the upgrade of the Arna railway station.

show abstract

Section: Incremental Verificationmentioning

confidence: 99%

Efficient verification of railway infrastructure designs against standard regulations

Luteberget

Johansen

2017

Form Methods Syst Des

View full text Add to dashboard Cite

show abstract

“…View maintenance in conventional client/server and data warehouse environments has been addressed to a large extent (Gupta et al, 1993;Bailey et al, 1995;Zhuge et al, 1995). In general, view maintenance mechanisms could be classified into immediate update and periodic update mechanisms.…”

Section: Related Workmentioning

confidence: 99%

“…In Gupta et al (1993) the idea of associating a count attribute with each tuple in a view is proposed to avoid ambiguous view updating. The count attribute of a tuple defines the number of tuples in the deriving relations that derive the associated tuple.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Incremental View Maintenance for Mobile Databases

Lee

Leong

2000

Knowledge and Information Systems

View full text Add to dashboard Cite

In a mobile environment, querying a database at a stationary server from a mobile client is expensive due to the limited bandwidth of a wireless channel and the instability of the wireless network. We address this problem by maintaining a materialized view in a mobile client's local storage. Such a materialized view can be considered as a data warehouse. The materialized view contains results of common queries in which the mobile client is interested. In this paper, we address the view update problem for maintaining the consistency between a materialized view at a mobile client and the database server. The content of a materialized view could become incoherent with that at the database server when the content of the database server and/or when the location of the client is changed. Existing view update mechanisms are 'push-based'. The server is responsible for notifying all clients whose views might be affected by the changes in database or the mobility of the client. This is not appropriate in a mobile environment due to the frequent wireless channel disconnection. Furthermore, it is not easy for a server to keep track of client movements to update individual client location-dependent views. We propose a 'pull-based' approach that allows a materialized view to be updated at a client in an incremental manner, requiring a client to request changes to its view from the server. We demonstrate the feasibility of our approach with experimental results.

show abstract

“…However, the difficulty and complexity of a view maintenance approach is dependent on the underlying data model. Although there have been man studies on view maintenance and materialization within the relational model [7,8], much effort is still required on view maintenance within the nested relational model and object-oriented data models in addition to the effort done in this respect e.g. [1,2,6,9,10,11].…”

Section: Introductionmentioning

confidence: 99%

View maintenance in object-oriented databases

Alhajj

Polat

1996

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. In this paper, we present a model that facilitates view maintenance within object-oriented databases. For that purpose, we differentiate between two categories of classes, base classes and brother classes. While the former constitute the actual database, the latter are introduced to hold virtual database, i.e., views derived from base classes. To achieve incremental view update, we introduce a modification list into each base class. A series of algorithms are developed to serve the purpose. Finally it happened that, view maintenance within object-oriented databases subsumes that within the nested and hence conventional relationai models.

show abstract

Maintaining views incrementally

Cited by 449 publications

References 14 publications

Efficient verification of railway infrastructure designs against standard regulations

Efficient verification of railway infrastructure designs against standard regulations

Incremental View Maintenance for Mobile Databases

View maintenance in object-oriented databases

Contact Info

Product

Resources

About