Demo Data from VLDB 2026 / reviewers in the wild / expert
Adi Unnithan
dblp:06/8166
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 2010
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 2
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 |
Data models and query languages · 50% Data integration and cleaning · 50% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data integration and cleaning › schema mapping
object-relational mapping |
0.1 | 1 | 2010 | Worry-free database upgrades: automated model-driven evolution of schemas and complex mappings · SIGMOD Conference 2010 |
Data models and query languages › schema management
schema evolution |
0.1 | 1 | 2010 | Worry-free database upgrades: automated model-driven evolution of schemas and complex mappings · SIGMOD Conference 2010 |
Methods — techniques the papers use, named apart from their topics
model-driven engineering · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2010 | Automated Co-evolution of Conceptual Models, Physical Databases, and Mappings
James F. Terwilliger, Philip A. Bernstein, Adi Unnithan |
ER | 3 |
| 2010 | Worry-free database upgrades: automated model-driven evolution of schemas and complex mappingsabstractSchema evolution is an unavoidable consequence of the application development lifecycle. The two primary schemas in an application, the client conceptual object model and the persistent database model, must co-evolve or risk quality, stability, and maintainability issues. We present MoDEF, an extension to Visual Studio that supports automatic evolution of object-relational mapping artifacts in the Microsoft Entity Framework. When starting with a valid mapping between client and store, MoDEF translates changes made to a client model into incremental changes to the store as an upgrade script, along with a new valid mapping to the new store. MoDEF mines the existing mapping for mapping patterns which MoDEF reuses for new client artifacts. James F. Terwilliger, Philip A. Bernstein, Adi Unnithan |
SIGMOD Conference | 3 |