From 619a3ea1fe123900bfc19738f63b9ebae79a22f4 Mon Sep 17 00:00:00 2001
From: Matt <1009003+tantaman@users.noreply.github.com>
Date: Fri, 13 Oct 2023 08:37:09 -0400
Subject: [PATCH] read perms plan

---
 notes.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/notes.md b/notes.md
index 623f58b1f..b81bd105f 100644
--- a/notes.md
+++ b/notes.md
@@ -16,6 +16,13 @@ Each `col_version` is currently incremented independently. We can instead set it
 
 This isn't guaranteed since the peer being merged into could be way ahead in db_version overall but have some records behind in db_version.
 
+# read perms
+
+- callback
+- gets invoked when returning from `crsql_changes`
+- can be manually invoke by user for manual sync queries. e.g., `AND crsql_rls('table', pks...)`? No need to do this ever?
+- partial sync is user query -> perm fail find -> crsql_changes (based on lowest db version found from prior perm failures)
+
 # pk-lookup
 
 - New table