EDBT 2026 Demo / reviewers in the wild / expert
Aravindan Kasthurirangan
dblp:06/6967
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2001
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
1 paper |
Database theory · 44% Spatial and temporal data management · 44% Indexing and storage engines · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Database theory › integrity constraints
integrity constraint checking |
0.0 | 1 | 2001 | Efficient Sequenced Integrity Constraint Checking · ICDE 2001 |
Spatial and temporal data management
temporal databases |
0.0 | 1 | 2001 | Efficient Sequenced Integrity Constraint Checking · ICDE 2001 |
Indexing and storage engines
b+-tree |
0.0 | 1 | 2001 | Efficient Sequenced Integrity Constraint Checking · ICDE 2001 |
Methods — techniques the papers use, named apart from their topics
straight traversal · 0.0interval-tree overlap · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2001 | Efficient Sequenced Integrity Constraint CheckingabstractPrimary key and referential integrity are the most widely used integrity constraints in relational databases. Each has a sequenced analogue in temporal databases, in which the constraint must apply independently at every point in time. In this paper, we assume a stratum approach, which expresses the checking in conventional SQL, as triggers on period-stamped relations. We evaluate several novel approaches that exploit B/sup +/-tree indexes to enable efficient checking of sequenced primary key (SPK) and sequenced referential integrity (SRI) constraints. We start out with a brute-force SPK algorithm, then adapt the relational interval-tree overlap algorithm. After that, we propose a new method, the straight traversal algorithm, which utilizes the B/sup +/-tree more directly in order to identify when multiple key values are present. Our evaluation, on two platforms, shows that the straight traversal algorithm approaches the performance of built-in nontemporal primary key and referential integrity checking, with a constant time per tuple. Richard T. Snodgrass, Shiyan Deng, Vineel Kumar Gattu, Aravindan Kasthurirangan |
ICDE | 5 |