Skip to content
Snippets Groups Projects
Verified Commit 936ee2d6 authored by Timm Fitschen's avatar Timm Fitschen
Browse files

DOC: update docs for new behavior of FIND queries

parent 86722bad
Branches
Tags
2 merge requests!96Release 0.11.2,!82DOC: F find query
Pipeline #30784 passed
...@@ -69,8 +69,9 @@ Examples ...@@ -69,8 +69,9 @@ Examples
c.insert() c.insert()
# Useful for testing: wait until the user presses a key # Useful for testing: wait until the user presses a key
# Meanwhile have a look at the WebUI: You can e.g. query "FIND Test*" to view # Meanwhile have a look at the WebUI: You can e.g. query "FIND ENTITY Test*"
# all the entities created here and see the relations and links between them. # to view all the entities created here and see the relations and links
# between them.
b = input("Press any key to cleanup.") b = input("Press any key to cleanup.")
# cleanup everything after the user presses any button. # cleanup everything after the user presses any button.
c.delete() c.delete()
...@@ -25,7 +25,7 @@ However, you can also translate the examples to the data model that you have at ...@@ -25,7 +25,7 @@ However, you can also translate the examples to the data model that you have at
Let's start with a simple query. Let's start with a simple query.
>>> response = db.execute_query("FIND RECORD Guitar") >>> response = db.execute_query("FIND Guitar")
Queries work the same way as in the web interface. You simply provide the Queries work the same way as in the web interface. You simply provide the
query string to the corresponding function (``db.execute_query``). However, the result is not query string to the corresponding function (``db.execute_query``). However, the result is not
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment