Query Validation with Automated Scope Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing query validation systems often block sensitive queries, leading to inefficiencies and increased database traffic due to repeated failed attempts, without providing clear explanations to users, and may disrupt workflows, especially in scenarios where queries are inadvertently sensitive.
Innovation Solution
A computing system that iteratively modifies sensitive queries by increasing their scope, updates estimated query results, and determines sensitivity based on these modifications, allowing the query to proceed once it is no longer sensitive, thereby improving query efficiency and user notification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If sensitive queries are blocked, then privacy protection is improved, but query efficiency and database utility deteriorate
Solution Approach 1:
The system converts blocked sensitive queries into modified non-sensitive queries by automatically generalizing the query scope. Instead of simply rejecting sensitive queries, the system modifies them to increase scope (e.g., changing specific time ranges or location parameters) and submits the modified version, thereby transforming a harmful blocking action into a beneficial query transformation that preserves both privacy and utility.
Solution Approach 2:
The system changes query parameters by automatically modifying query scope parameters such as time ranges, location boundaries, or data granularity. When a query is detected as sensitive, the system adjusts these parameters to broaden the scope and reduce sensitivity, allowing the query to proceed while maintaining privacy protection.
2Object-affected harmful factors
If sensitive queries are blocked, then privacy protection is improved, but database traffic increases due to repeated failed attempts
Solution Approach 1:
The system performs preliminary query modification before submission by automatically detecting sensitivity and adjusting query scope in advance. This preliminary action prevents the need for repeated failed query attempts, as the modified query is designed to be non-sensitive from the start, thereby reducing overall database traffic while maintaining privacy protection.
3Object-affected harmful factors
If sensitive queries are blocked, then privacy protection is improved, but workflow disruption increases
Solution Approach 1:
The system provides self-service by automatically detecting sensitive queries and performing the necessary modifications without requiring user intervention. The system independently identifies sensitivity issues, adjusts query parameters, and resubmits modified queries, thereby maintaining workflow continuity while protecting privacy, without disrupting the user's operational flow.
Data Source
AI summary
Disclosed herein are embodiments providing query validation with automated query modification. In particular, the embodiments provide a computing system that receives a query and determines the query is sensitive. The computing system iteratively modifies the query until the query is not sensitive by modifying the query to increase a scope of the query, updating estimated query results based on the query as modified, and determining whether the query as modified is sensitive based on the estimated query results as updated. Upon determining that the query as modified is not sensitive, the computing system proceeds with the query as modified. Accordingly, the computing system improves query efficiency by automatically modifying a sensitive query.