Demo Data from EDBT 2026 / reviewers in the wild / expert
Tianyin Pan
dblp:147/1225
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2014
—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 |
Information retrieval · 56% Data models and query languages · 44% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data models and query languages
query language design |
0.2 | 1 | 2014 | Schema-free SQL · SIGMOD Conference 2014 |
Information retrieval › cross-language information retrieval
query translation |
0.2 | 1 | 2014 | Schema-free SQL · SIGMOD Conference 2014 |
Information retrieval › keyword search
keyword search over relational databases |
0.1 | 1 | 2014 | Schema-free SQL · SIGMOD Conference 2014 |
Methods — techniques the papers use, named apart from their topics
schema inference · 0.2query rewriting · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2014 | Schema-free SQLabstractQuerying data in relational databases is often challenging since SQL requires its users to know the exact schema of the database, the roles of various entities in a query, and the precise join paths to be followed. On the other hand, keyword search is unable to express much desired query semantics. In this paper, we propose a query language, Schema-free SQL, which enables its users to query a relational database using whatever partial schema they know. If they know the full schema, they can write full SQL. But, to the extent they do not know the schema, Schema-free SQL is tolerant of unknown or inaccurately specified relation names and attribute names, and it also does not require information regarding which relations are involved and how they are joined. We present techniques to evaluate Schema-free SQL by first converting it to full SQL. We show experimentally that a small amount of schema information, which one can reasonably expect most users to have, is enough to get queries evaluated as if they had been completely and correctly specified. Tianyin Pan, H. V. Jagadish |
SIGMOD Conference | 2 |