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
docs(sql): fix 'v' field documentation inconsistency in count_encrypted_with_active_config
**Problem:**
Documentation incorrectly stated that the 'v' field stores the active
configuration ID, contradicting src/encrypted/constraints.sql:56 which
correctly documents that 'v' must be the literal payload version "2".
**Root Cause:**
The 'v' field serves a single, consistent purpose across the entire
codebase: it stores the EQL payload format version (currently "2").
It does NOT store configuration IDs.
**Fix:**
- Removed incorrect claim that 'v' stores configuration ID
- Clarified that 'v' field stores payload version "2"
- Updated function description to avoid implementation details
- Added note explaining the distinction
**Files Changed:**
- src/encryptindex/functions.sql:201-209
**Verification:**
- ✅ All tests passing (59 test files)
- ✅ Documentation now consistent with src/encrypted/constraints.sql:56
- ✅ No code changes - documentation-only fix
**Context:**
This addresses feedback about major documentation inconsistency where
two different files made contradictory claims about the 'v' field's
purpose. The payload version is always "2" for EQL v2, as enforced by
the _encrypted_check_v validation function.
0 commit comments