Transaction management with integrity checking

Davide Martinenghi, Henning Christiansen

    Publikation: Bidrag til bog/antologi/rapportKonferencebidrag i proceedingsForskningpeer review

    Abstract

    Database integrity constraints, understood as logical conditions that must hold for any database state, are not fully supported by current database technology. It is typically up to the database designer and application programmer to enforce integrity via triggers or tests at the application level, which are difficult to maintain and error prone. Two important aspects must be taken care of. 1.~It is too time consuming to check integrity constraints from scratch after each update, so simplified checks before each update should be used relying on the assumption that the current state is consistent. 2.~In concurrent database systems, besides the traditional correctness criterion, the execution schedule must ensure that the different transactions can overlap in time without destroying the consistency requirements tested by other, concurrent transactions.
    OriginalsprogEngelsk
    TitelProc. DEXA 2005, 16th International Conference on Database and Expert Systems Applications
    RedaktørerK. V. Andersen, J. Debenham, R. Wagner
    Antal sider10
    ForlagSpringer
    Publikationsdato2005
    Sider606-615
    ISBN (Trykt)3-540-28566-0
    StatusUdgivet - 2005
    BegivenhedInternational Conference on Database and Expert Systems Applications - København, Danmark
    Varighed: 22 aug. 200526 aug. 2005
    Konferencens nummer: 16

    Konference

    KonferenceInternational Conference on Database and Expert Systems Applications
    Nummer16
    LandDanmark
    ByKøbenhavn
    Periode22/08/200526/08/2005
    NavnLecture Notes in Computer Science
    Vol/bind3588
    ISSN0302-9743

    Citer dette