From 95cbf0eb00b8a086956ecaab44812b38729256ba Mon Sep 17 00:00:00 2001 From: jonathan2384 <93066841+jonathan2384@users.noreply.github.com> Date: Thu, 25 Nov 2021 00:29:27 +0900 Subject: [PATCH] Update fundamentaldifferences.md --- migrating/notion/fundamentaldifferences.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migrating/notion/fundamentaldifferences.md b/migrating/notion/fundamentaldifferences.md index 89db575..69e95fe 100644 --- a/migrating/notion/fundamentaldifferences.md +++ b/migrating/notion/fundamentaldifferences.md @@ -73,7 +73,7 @@ If you want to read further about the advantages and disadvantages a non-hierarc Notion's relational databases are an incredibly flexible tool to help you categorize, organize, and **store** database entries - each of which is a fully-functioning page. Anytype works differently, yet, you can achieve the same (and more) with Anytype's Sets, Types and Relations. ## Sets and Relations -![image.png](<../.gitbook/assets/notiondb.png) +![image.png](<../.gitbook/assets/notiondb.png>) *Here's a Notion database. Each database entry is a page, and has predefined **properties, such as Tags, URL, and Phone**.* Anytype's equivalent to Notion's databases are Sets. Unlike Notion databases, Sets do not **store** objects. Instead, they **show**, not store, all objects which meet a specific criteria, kind of how search works. Currently, sets can only show objects with one specific Type relation. Don't know what a Relation is? We'll cover it shortly.