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: README.md
+2-90Lines changed: 2 additions & 90 deletions
Original file line number
Diff line number
Diff line change
@@ -341,96 +341,8 @@ SELECT field, COUNT(*) FROM users GROUP BY field;
341
341
342
342
## JSON and JSONB support
343
343
344
-
EQL supports encrypting, decrypting, and searching JSON and JSONB objects.
345
-
346
-
### Configuring the index
347
-
348
-
Similar to how you configure indexes for text data, you can configure indexes for JSON and JSONB data.
349
-
The only difference is that you need to specify the `cast_as` parameter as `json` or `jsonb`.
350
-
351
-
```sql
352
-
SELECT cs_add_index_v1(
353
-
'users',
354
-
'encrypted_json',
355
-
'ste_vec',
356
-
'jsonb',
357
-
'{"prefix": "users/encrypted_json"}'-- The prefix is in the form of "table/column"
358
-
);
359
-
```
360
-
361
-
You can read more about the index configuration options [here](https://github.com/cipherstash/encrypt-query-language/blob/main/docs/reference/INDEX.md).
362
-
363
-
### Inserting JSON data
364
-
365
-
When inserting JSON data, this works the same as inserting text data.
366
-
You need to wrap the JSON data in the appropriate EQL payload.
367
-
CipherStash Proxy will **encrypt** the data automatically.
368
-
369
-
**Example:**
370
-
371
-
Assuming you want to store the following JSON data:
0 commit comments