User Tools

Site Tools


sql-derivative-sensitivity-analyser

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
sql-derivative-sensitivity-analyser [2019/05/31 17:38]
alisa [Quick guide]
sql-derivative-sensitivity-analyser [2019/05/31 17:54]
alisa [Quick guide]
Line 18: Line 18:
 Clicking on a task opens two window tabs on the right side of the page (in sidebar): **Output table schema** and **Output table query**. Clicking on a task opens two window tabs on the right side of the page (in sidebar): **Output table schema** and **Output table query**.
  
-The tab **Output table schema** expects ​the schema of the table that comes out as the result of computation in the given task.+The tab **Output table schema** expects schema of the table that comes out as the result of computation in the given task. The schema description comes in SQL language in form of a CREATE TABLE statement.
  
 +<​code>​
 +CREATE TABLE t (
 +  var_1 type_1,
 +  ...
 +  var_n type_n
 +);
 +</​code>​
  
-The tab **Output table query** expects an SQL SELECT-statement as an input. As the goal of CS analyzer is to ensure differential privacy by adding noise to the final output of an SQL workflow, the **last task** (the one followed by a end event) should return a numerical value, i.e the output of that task should be an aggregation. Grouping by a table attribute (but not a complex expression) is allowed. The analyzer expects that the group columns come first, and the aggregation is the last one. Currently supported aggregations are COUNT, SUM, MIN, MAX, and only one aggregation per task is allowed.+The analyzer supports all data types that the underlying PSQL engine recognizes. However, only those starting with "​int"​ and "​float"​ are interpreted as numerical. All the other data types are treated as strings. 
 + 
 +The tab **Output table query** expects an SQL SELECT-statement as an input. The output of this statement should be compatible with the schema described in **Output table schema**. As the goal of CS analyzer is to ensure differential privacy by adding noise to the final output of an SQL workflow, the **last task** (the one followed by a end event) should return a numerical value, i.e the output of that task should be an aggregation. Grouping by a table attribute (but not a complex expression) is allowed. The analyzer expects that the group columns come first, and the aggregation is the last one. Currently supported aggregations are COUNT, SUM, MIN, MAX, and only one aggregation per task is allowed.
  
 <​code>​ <​code>​
sql-derivative-sensitivity-analyser.txt · Last modified: 2019/10/01 17:22 by alisa