Demo Data from VLDB 2026 / reviewers in the wild / expert
Simon Rink
dblp:421/4613
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2025
0009-0003-0361-4809ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 1 · 1 first-author · 1 since 2021
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 |
Query processing and optimization · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Query processing and optimization › query planning
query plan enumeration |
0.9 | 1 | 2025 | Query Optimization for Database-Returning Queries · Proc. ACM Manag. Data 2025 |
Query processing and optimization › query planning
query plan selection |
0.9 | 1 | 2025 | Query Optimization for Database-Returning Queries · Proc. ACM Manag. Data 2025 |
Query processing and optimization
semijoin reduction |
0.3 | 1 | 2025 | Query Optimization for Database-Returning Queries · Proc. ACM Manag. Data 2025 |
Methods — techniques the papers use, named apart from their topics
semi-join reduction · 0.9enumeration algorithm · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Query Optimization for Database-Returning QueriesabstractRecently, the novel concept of database-returning SQL queries (DRQs) was introduced. Instead of a single, (potentially) denormalized result table, DRQs return an entire subdatabase with a single SQL query. This subdatabase represents a subset of the original database, reduced to the relations, tuples, and attributes that contribute to the traditional join result. DRQs offer several benefits: they reduce network traffic in client-server settings, can lower memory requirements for materializing results, and significantly simplify querying hierarchical data. Currently, two state-of-the-art algorithms exist to compute DRQs: (1.) ResultDB Semi-Join builds upon Yannakakis' semi-join reduction algorithm by adding support for cyclic queries. (2.) ResultDB Decompose computes the standard single-table result and projects the result to the base tables to obtain the resulting subdatabase. However, multiple issues can be identified with these algorithms. First, ResultDB Semi-Join employs simple heuristics to greedily solve the underlying enumeration problems, often leading to suboptimal query plans. Second, each algorithm performs best under different conditions, so it is up to the user to choose the appropriate one for a given scenario. In this paper, we address these two issues. We propose two enumeration algorithms for ResultDB Semi-Join to handle the Root Node Enumeration Problem (RNEP) and the Tree Folding Enumeration Problem (TFEP). Further, we present a unified enumeration algorithm, TD ResultDB , to automatically decide between plans generated by our new enumeration algorithms for ResultDB Semi-Join and ResultDB Decompose . Through a comprehensive experimental evaluation, we show that the enumeration time overhead introduced by our methods remains minimal. Furthermore, by effectively solving the RNEP and TFEP, we achieve up to a 6x speed-up in query execution time for ResultDB textSemi-Join , whereas TD ResultDB consistently selects the best available plans. Simon Rink, Jens Dittrich |
Proc. ACM Manag. Data | 1 |