Proceedings of the 37th ACM SIGMOD-SIGACT-SIGAI Symposium on Principles of Database Systems 2018
DOI: 10.1145/3196959.3196965
|View full text |Cite
|
Sign up to set email alerts
|

When Can We Answer Queries Using Result-Bounded Data Interfaces?

Abstract: We consider answering queries on data available through access methods, that provide lookup access to the tuples matching a given binding. Such interfaces are common on the Web; further, they often have bounds on how many results they can return, e.g., because of pagination or rate limits. We thus study result-bounded methods, which may return only a limited number of tuples. We study how to decide if a query is answerable using result-bounded methods, i.e., how to compute a plan that returns all answers to th… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
20
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
3
2
2

Relationship

2
5

Authors

Journals

citations
Cited by 11 publications
(21 citation statements)
references
References 37 publications
1
20
0
Order By: Relevance
“…In the context of relational databases, several approaches have been proposed for enabling secure collaborative computations over data. Traditional solutions can be based on the definition of views (e.g., [35,46]), representing portions of a dataset for which different subjects are authorized, or on access patterns (e.g., [3,5]), restricting the data that can be accessed based on the input that is provided by a subject. Such solutions however only capture the information that is explicitly involved in the computation, while a computation may also leak information not explicitly visible.…”
Section: Collaborative Computationsmentioning
confidence: 99%
“…In the context of relational databases, several approaches have been proposed for enabling secure collaborative computations over data. Traditional solutions can be based on the definition of views (e.g., [35,46]), representing portions of a dataset for which different subjects are authorized, or on access patterns (e.g., [3,5]), restricting the data that can be accessed based on the input that is provided by a subject. Such solutions however only capture the information that is explicitly involved in the computation, while a computation may also leak information not explicitly visible.…”
Section: Collaborative Computationsmentioning
confidence: 99%
“…Towards our characterization, we combine a technique known as linearization [18], which converts a set of guarded TGDs into a set of linear TGDs, with simplification used in the previous section. Linearization is a very useful technique that has found several applications in the context of query answering [2,4,5,18,19]. This is the first time, however, that it is used in the context of chase termination.…”
Section: Guarded Tgdsmentioning
confidence: 99%
“…The problem of managing queries in distributed scenarios has been extensively studied, but traditional solutions (e.g., [19,21]) as well as modern approaches that consider big data analytics (e.g., [2,4,25]) do not take into consideration access restrictions. In the relational database context, access restrictions can be supported by views (e.g., [9,17,26]), access patterns (e.g., [3,6]), or data masking (e.g., [20]). Such proposals however do not consider encryption.…”
Section: Related Workmentioning
confidence: 99%