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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,18 +22,18 @@ This is a very specific library to do one specific thing - get list items from a
22
22
23
23
But let me try to sell camlsql to you anyway.
24
24
25
-
- camlsql is **lightweight** - only 8.3 KB min+gz
26
-
- Generate CAML queries using **SQL-like syntax**! SQL! Too easy!
27
-
-**No dependencies** other than the existing SharePoint CSOM libraries
28
-
- SQL syntax (yes, I mention it again) and no need to manually build XML strings
25
+
- camlsql is ***lightweight*** - only 8.3 KB min+gz
26
+
- Generate CAML queries using ***SQL-like syntax***! SQL! Too easy!
27
+
-***No dependencies*** other than the existing SharePoint CSOM libraries
28
+
-***SQL syntax*** (yes, I mention it again) and no need to manually build XML strings
29
29
30
30
Not convinced? I figured as much... Read on...
31
31
32
32
#### Why choose CSOM over REST?
33
33
34
34
Other than my above attempts to convice you there are few "actual" reasons when you may need to use CamlQueries over the SharePoint REST API.
35
35
36
-
-**Nested joins** is not supported by the REST API
36
+
-***Nested joins*** is not supported by the REST API
37
37
- If you have list **A** with a lookup field to list **B**,<br>and list **B** has a lookup field to **C** - then you can not query list **A** and join list C via list B.
38
38
- This is possible using CAML and by using [JOIN](https://dlid.github.io/camlsql-js/#/sql?id=joining-a-second-list) in the camlsql library
39
39
-***Calculated fields*** can not be queried using the REST API
0 commit comments