You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user_guide.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Tables may have one of two security labels, `public` or `personal`.
59
59
* Tables labeled as `personal` are anonymized by the extension (for `anonymized_trusted` and `anonymized_untrusted` users, not `direct` users).
60
60
* Tables labeled as `public` are not anonymized: all users have full access to these tables.
61
61
62
-
The procedure `diffix.mark_public(namespace, table_name)` labels a table as `public`.
62
+
The procedure `diffix.mark_public(table_name)` labels a table as `public`.
63
63
64
64
Note that unlabeled tables can not be queried by `anonymized_trusted` and `anonymized_untrusted` users (unless the setting variable `pg_diffix.treat_unmarked_tables_as_public` is set to `true`).
65
65
@@ -71,18 +71,18 @@ Each protected entity must have at least one column that contains the identifier
71
71
72
72
__NOTE:__ if AID columns are not correctly labeled, the extension may fail to anonymize appropriately.
73
73
74
-
The procedure `diffix.mark_personal(namespace, table_name, aid_columns...)` is used to label a table as personal and to label its AID columns.
74
+
The procedure `diffix.mark_personal(table_name, aid_columns...)` is used to label a table as personal and to label its AID columns.
0 commit comments