Wir verwenden Cookies und Google Analytics um ihnen ein besseres Internet-Erlebnis zu ermöglichen und unseren Website-Traffic zu analysieren um zu verstehen, woher unsere Besucher kommen. Details siehe Datenschutzerklärung

Preferences Example


When working with multiple databases – possibly on multiple servers – it can be hard to know which DB you are currently connected to. As you have also seen in the previous chapters, there are several locations in the UI where neo4j Commander needs to show nodes and relationships and by default it does this in a rather random fashion BUT you can use Preferences to optimize your experience and productivity drastically.

Select “Preferences” from the main menu (top left):

You can set these preferecens according to your data schema to optimize the UI/UX. And since these settings are so tighlty related to the data model of your DB, these preferences are stored inside the DB in a special “N2Neo4j” node. This way everyone connecting to that DB with neo4j Commander immediately gets an optimized user experience.

Note: The query history, last opened editos and bookmarks are stored in the browser’s storage on a per-database basis.

Tip: If you are using OGM/SDN to map classes to DB nodes, the nodes are automatically assigned labels for the object’s class and all super classes. E.g. a User class might be derived from AbstractUser which in turn is derived from AbstractEntity. Use the “Hidden Labels” feature set to “AbstractEntity, AbstractUser” to hide those labels and avoid visual clutter.