Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify SQL database in collections doc #1553

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
3 changes: 2 additions & 1 deletion markdoc.config.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,8 @@
"watch": true
},
"partials": {
"auth-security.md": "./src/partials/auth-security.md"
"auth-security.md": "./src/partials/auth-security.md",
"cli-disclaimer.md": "./src/partials/cli-disclaimer.md"
ebenezerdon marked this conversation as resolved.
Show resolved Hide resolved
}
}
]
3 changes: 2 additions & 1 deletion src/routes/docs/products/databases/collections/+page.markdoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,8 @@ title: Collections
description: Organize your data with Appwrite Collections. Explore how to create and configure collections to store and structure your data effectively.
---
Appwrite uses collections as containers of documents. Each collection contains many documents identical in structure.
The terms collections and documents are used because the Appwrite JSON REST API resembles the API of a traditional NoSQL database.
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.
ebenezerdon marked this conversation as resolved.
Show resolved Hide resolved

That said, Appwrite is designed to support both SQL and NoSQL database adapters like MariaDB, MySQL, or MongoDB in future versions.

Expand Down
Loading