Clarify SQL database in collections doc #1553
Open
+4
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The preview deployment is ready. 🟢 Open Preview | Open Build Logs Last updated at: 2024-12-13 19:36:23 CET |
stnguyen90
requested changes
Dec 12, 2024
Comment on lines
7
to
8
| While Appwrite uses SQL, the terms collections and documents are used because the Appwrite JSON REST API resembles | ||
| the API of a traditional NoSQL database, making it intuitive and user-friendly. |
There was a problem hiding this comment.
To make this flow better with the previous sentence, I focus on the terms first rather than saying "Appwrite uses SQL" first.
There was a problem hiding this comment.
Got it. How's the new update?
adityaoberai
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
cli-disclaimerpartial path to markdoc config