Demo Data from EDBT 2026 / reviewers in the wild / expert
Miguel Cunha
dblp:76/1465
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2003
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Computer networks · 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 |
Transaction processing and concurrency control · 50% Distributed and cloud data management · 50% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed and cloud data management › mobile data management
mobile databases |
0.0 | 1 | 2003 | Reservations for Conflict Avoidance in a Mobile Database System · MobiSys 2003 |
Transaction processing and concurrency control › transaction models
mobile transactions |
0.0 | 1 | 2003 | Reservations for Conflict Avoidance in a Mobile Database System · MobiSys 2003 |
Methods — techniques the papers use, named apart from their topics
reservations · 0.0PL/SQL · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2003 | Reservations for Conflict Avoidance in a Mobile Database SystemabstractMobile computing characteristics demand data management systems to support independent operation. However, the execution of updates in a mobile client usually need to be considered tentative because uncoordinated updates that conflict need to be reconciled. In this paper we present a mechanism to independently guarantee that updates can be executed in the server without conflicts. To this end, clients obtain leased reservations upon the database state. Updates are specified as common small PL/SQL programs, dubbed mobile transactions, that execute both in the mobile client and in the server. Using the available reservations, the client transparently verifies that a transaction can be executed in the same way both in the mobile client and in the server, thus leading to the same final result. Mobile transactions may specify conflict detection and resolution rules to be used when transactions cannot be locally guaranteed. Nuno M. Preguiça, José Legatheaux Martins, Miguel Cunha, Henrique João L. Domingos |
MobiSys | 3 |