Skip to content

Commit beaacef

Browse files
authored
Fix URL in the graph DBs vs TypeDB comparison page (typedb#537)
1 parent f62b17e commit beaacef

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

12-comparisons/02-graph-databases-and-typedb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The main differences between TypeDB and graph databases can be summarised as:
1616
2. **TypeDB contains a built-in automated reasoner**, graph databases don't provide native reasoning capabilities
1717
3. **TypeDB is an abstraction layer over a graph.** TypeDB leverages a graph database under the hood to create a higher-level abstraction, resulting in both technologies working at different levels of abstraction
1818

19-
There are several different graph technologies available. Some of these are based on RDF and SPARQL, others are imperative, path-based query languages based on Gremlin. Most popular, however, is Cypher, which has grown to become the most adopted graph database query language for property graphs. For this reason, in this comparison we'll just focus on Cypher and labelled property graphs. For a comparison of TypeDB to Semantic Web Technologies, you can read [this](https://docs.vaticle.com/docs/comparisons/semantic-web-and-typeql).
19+
There are several different graph technologies available. Some of these are based on RDF and SPARQL, others are imperative, path-based query languages based on Gremlin. Most popular, however, is Cypher, which has grown to become the most adopted graph database query language for property graphs. For this reason, in this comparison we'll just focus on Cypher and labelled property graphs. For a comparison of TypeDB to Semantic Web Technologies, you can read [this](https://docs.vaticle.com/docs/comparisons/semantic-web-and-typedb).
2020

2121
## The Challenges of Working with a Graph Database
2222

0 commit comments

Comments
 (0)