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: new_home/modules/ROOT/pages/get_started/data.adoc
-6Lines changed: 0 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -177,10 +177,7 @@ Studio::
177
177
In order to insert a friendship, we need to refer to users that will play the role of friends in the friendship.
178
178
That's where variables come into play!
179
179
180
-
[Note]
181
-
-----
182
180
Recall that each friendship takes exactly two friends as specified in the schema; feel free to experiment though, and see what error messages TypeDB will give you when trying to insert triple friendships.
183
-
-----
184
181
185
182
[,typeql]
186
183
----
@@ -201,10 +198,7 @@ Console::
201
198
In order to insert a friendship, we need to refer to users that will play the role of friends in the friendship.
202
199
That's where variables come into play!
203
200
204
-
[Note]
205
-
-----
206
201
Recall that each friendship takes exactly two friends as specified in the schema; feel free to experiment though, and see what error messages TypeDB will give you when trying to insert triple friendships.
The fetch clause lets you lay out the exact JSON document you need for your application, making it easy to retrieve additional data such as optional attributes or answers from subqueries.
659
-
660
659
--
661
660
Console::
662
661
+
@@ -685,38 +684,38 @@ fetch {
685
684
};
686
685
# end::fetch1[]
687
686
688
-
# tag::fetch_1_result[]
687
+
# tag::fetch1_result[]
689
688
{
689
+
"username": "alice",
690
690
"friends": [
691
691
{
692
-
"friend": "bob78"
692
+
"friend": "bob"
693
693
},
694
694
{
695
-
"friend": "deltaonenine"
695
+
"friend": "delta"
696
696
}
697
-
],
698
-
"username": "alice1925"
697
+
]
699
698
}
700
699
{
700
+
"username": "bob",
701
701
"friends": [
702
702
{
703
-
"friend": "alice1925"
703
+
"friend": "alice"
704
704
},
705
705
{
706
-
"friend": "deltaonenine"
706
+
"friend": "delta"
707
707
}
708
-
],
709
-
"username": "bob78"
708
+
]
710
709
}
711
710
{
712
-
"username": "candice001",
711
+
"username": "charlene",
713
712
"friends": [
714
713
{
715
-
"friend": "deltaonenine"
714
+
"friend": "delta"
716
715
}
717
716
]
718
717
}
719
-
#end::fetch_1_result[]
718
+
#end::fetch1_result[]
720
719
----
721
720
////
722
721
[,typeql]
@@ -725,11 +724,19 @@ fetch {
725
724
include::./query-composition.adoc[tag=fetch1]
726
725
----
727
726
728
-
The fetch clause lets you lay out the exact JSON document you need for your application, making it easy to retrieve additional data such as optional attributes or answers from subqueries.
727
+
This query now returns a sequence of JSON documents:
The fetch clause lets you lay out the exact JSON document you need for your application, making it easy to retrieve additional data such as optional attributes or answers from subqueries.
738
+
739
+
733
740
== What next?
734
741
There is much more to explore in the world of TypeDB, including building custom query logic using disjunctions and negations, the deep exploration of data connection using functional recursion, and more.
Copy file name to clipboardExpand all lines: new_home/modules/ROOT/pages/get_started/schema.adoc
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -381,8 +381,7 @@ Don't forget to commit the transaction by typing `commit` and pressing kbd[Enter
381
381
382
382
TypeDB's type system re-thinks data models from first principles: it modularizes schemas into their "atomic" components. For example, you can add or remove roles and ownerships at any point in time, or edit specific annotations.
383
383
This makes it easy to migrate and combine data, and programmatically re-structure your database if necessary.
384
-
There is much more to explore. You can check out the xref:{page-version}@new_core_concepts::typeql/index.adoc[TypeQL Concepts] section for specific details,
385
-
but in the meantime let's summarize!
384
+
There is much more to explore. You can check out the xref:{page-version}@new_core_concepts::typeql/index.adoc[TypeQL Concepts] section for specific details.
386
385
387
386
Here's your entire schema so you can see it in one go:
0 commit comments