Skip to content

Commit d7b8932

Browse files
committed
Minor readme updates
1 parent 7af478e commit d7b8932

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,18 +22,18 @@ This is a very specific library to do one specific thing - get list items from a
2222

2323
But let me try to sell camlsql to you anyway.
2424

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
2929

3030
Not convinced? I figured as much... Read on...
3131

3232
#### Why choose CSOM over REST?
3333

3434
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.
3535

36-
- **Nested joins** is not supported by the REST API
36+
- ***Nested joins*** is not supported by the REST API
3737
- 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.
3838
- 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
3939
- ***Calculated fields*** can not be queried using the REST API

0 commit comments

Comments
 (0)