Thémis: a database programming language with integrity constraints

Benzaken, Véronique; Doucet, Anne

doi:10.1007/978-1-4471-3564-7_14

Cited by 6 publications

(9 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In particular, Benzaken and Doucet [36] dealt with ways in which to detect statically whether the execution of a method can potentially violate an integrity constraint, and introduced the ideas of identifying the portion of a schema manipulated by an update operation. As we have already pointed out, Liefke and Davidson [12] also address the problem of analyzing pairs of updates and query-update paths to detect possible sources of non-determinism.…”

Section: Methods Properties and Static Analysismentioning

confidence: 99%

A set‐oriented method definition language for object databases and its semantics

Bertino

Guerrini

Merlo

2003

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYIn this paper we propose a set-oriented rule-based method definition language for object-oriented databases. Most existing object-oriented database systems exploit a general-purpose imperative objectoriented programming language as the method definition language. Because methods are written in a general-purpose imperative language, it is difficult to analyze their properties and to optimize them. Optimization is important when dealing with a large amount of objects as in databases. We therefore believe that the use of an ad hoc, set-oriented language can offer some advantages, at least at the specification level. In particular, such a language can offer an appropriate framework to reason about method properties.In this paper, besides defining a set-oriented rule-based language for method definition, we formally define its semantics, addressing the problems of inconsistency and non-determinism in set-oriented updates. Moreover, we characterize some relevant properties of methods, such as conflicts among method specifications in sibling classes and behavioral refinement in subclasses.

show abstract

Section: Methods Properties and Static Analysismentioning

confidence: 99%

A set‐oriented method definition language for object databases and its semantics

Bertino

Guerrini

Merlo

2003

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

“…Furthermore, checking all related constraints after each transaction (even when it is not used) is prohibitively expensive. To reduce the overhead of monolithic runtime tests, it is suggested to prove at compile-time the fact that transactions respect integrity constraints [9,10,52].…”

Section: Related Workmentioning

confidence: 99%

Management of business process constraints using BPTrigger

Park

Choi

2004

Computers in Industry

View full text Add to dashboard Cite

“…Their main motivation is efficiency of consistency checking. Work done in this group provides techniques either to generate checking code for constraints specified declaratively [13,44,46] or explicitly specified in the conceptual model described using the entity relationship model or one of its extension [41,42,57] or to prove correctness of methods of classes and transactions w.r.t. integrity constraints [2,3,58].…”

Section: Related Workmentioning

confidence: 99%

Consistency management in object‐oriented databases

Oakasha

Conrad²,

Saake

2001

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYThe paper presents concepts and ideas underlying an approach for consistency management in objectoriented (OO) databases. In this approach constraints are considered as first class citizens and stored in a meta-database called constraints catalog. When an object is created constraints of this object are retrieved from the constraints catalog and relationships between these constraints and the object are established. The structure of constraints has several features that enhance consistency management in OO database management systems which do not exist in conventional approaches in a satisfactory way. This includes: monitoring object consistency at different levels of update granularity, integrity independence, and efficiency of constraints maintenance; controlling inconsistent objects; enabling and disabling constraints, globally to all objects or locally to individual objects; and declaring constraints on individual objects. All these features are provided by means of basic notations of OO data models.

show abstract

Thémis: a database programming language with integrity constraints

Cited by 6 publications

References 1 publication

A set‐oriented method definition language for object databases and its semantics

A set‐oriented method definition language for object databases and its semantics

Management of business process constraints using BPTrigger

Consistency management in object‐oriented databases

Contact Info

Product

Resources

About