Visualising Your Database

-

To show a visualisation of the Nodes and Relationships in your Neo4j instance, run the following in your Neo4j Browser:


CALL db.schema.visualisation()




Comments

Post a Comment

Popular posts from this blog

Property DataType - apoc.meta.type

-
Node Properties in Neo4j. A property can be of any datatype even within nodes of the same label. Nodes have no fixed schema as with the RDBMS where most notions of data storage are formed and 'best practice' is enforced.  Properties themselves do not have types, but the values they hold do. However, you can have a property, X which could be assigned a string value or a numeric value. There is no enforcement of typing for a property. Of course, it would not (always) make sense to assign a property different type values in your graph. So, just what datatype is the property? Trusty APOC has a function for that. WITH [true, 42, 'foo', 1.2] AS data UNWIND data as value RETURN apoc.meta.type(value) So, just what datatype is the property? "BOOLEAN" "INTEGER" "STRING" "FLOAT" You can use this function in MATCHES on nodes in your system where properties are unknown at runtime. MATCH (n:MyNode) RETURN apoc.meta.type(n.MyProperty)
Read more

Stopping and Starting the Neo4j Database

-
Controlling the service System services are controlled with the systemctl command. It accepts a number of commands and follows the format: systemctl {start|stop|restart} neo4j you may find that you need to prefix the systemctl command with sudo like: sudo systemctl stop neo4j looking at the output of the status command we get :   sudo systemctl status neo4j ● neo4j.service - Neo4j Graph Database    Loaded: loaded (/etc/systemd/system/neo4j.service; enabled; vendor preset: enabled)    Active: active (running) since Thu 2020-07-23 09:53:29 UTC; 1h 33min ago  Main PID: 958 (pre-neo4j.sh)     Tasks: 64    Memory: 14.3G       CPU: 22min 1.740s    CGroup: /system.slice/neo4j.service            ├─ 958 /bin/bash /etc/neo4j/pre-neo4j.sh            ├─ 996 /bin/sh /etc/neo4j/reset-password-aws.sh            ├─ 997 /usr/bin/java -cp /va...
Read more

MERGE made a new Node

-
MERGE is a powerful and misunderstood component of the CYPHER toolbox. Assume you have two :Person nodes each with a name property ('Adam' and 'Bob'). You might assume that you could MERGE as follows to create a [:KNOWS] relationship: MERGE (a:Person {name:'Adam'})-[r:KNOWS]->(b:Person {name:'Bob'}); and you'd be correct, it works perfectly Always remember MERGE is based on matching the entire pattern in the statement. Say you now want to set the age of Adam to 21 in the same statement. You might think it's as simple as MERGE (a:Person {name:'Adam',age:21})-[r:KNOWS]->(b:Person {name:'Bob'}); will create 2 new Person nodes and a [:KNOWS] relationship. If there is a unique constraint on :Person (name) there will be errors thrown and no new nodes or relationships. Why, the initial part of the MERGE 'looks' for a pattern match on the :Person node of name:'Adam' and age:21, it doesn't create a property. No m...
Read more