Manage Property Graphs
You can load a property graph into memory, share, edit, rename, delete or preview a graph.
- Click Graphs on the left navigation menu and navigate to the Graphs page.
- Select the Property Graph tab.You can see a list of property graphs for which you have access in the Autonomous Database as shown in the following figure.
Description of the illustration list_graphs.pngIn the preceding figure:
- The Type column indicates the type of the graph.
Graph Studio supports the creation of two types of property graphs:
- SQL Property Graph: The option to create a SQL property graph is available only if you are using an Autonomous Database instance with Oracle Database 23ai.
- PGQL Property Graph: The option to create a PGQL property graph is available on all types of tenancies and supported on all database versions.
- The In Memory column indicates the property graphs that are loaded into memory. You must ensure to load a full graph or selected properties into memory before accessing it, as the notebook interpreters operate only on the in-memory graphs. See Available Notebook Interpreters for more information on notebook interpreters.
- The Type column indicates the type of the graph.
- Select any property graph.The details of the graph are displayed in the graph details section of the Graphs page.
Note that this section also displays the previously computed Estimated In-Memory Graph Size.
- Optionally, click to perform any one of the following actions on the property graph:
Action Description To recompute the graph metadata to refresh metadata information about the graph which might have become stale, like the total number of vertices and edges. This action also recomputes and updates the Estimated In-Memory Graph Size. To rename the graph. To edit the graph. To share the graph with other users. To load the complete graph or selected properties into memory for analysis. Note:
Optionally, you can load a PGQL Property Graph by name directly in the notebook. See Load Graphs into Memory Programmatically for an example.When you click the Load Graph Into Memory icon, the Load Graph into memory slider is displayed:
Description of the illustration load_graph_into_memory.pngYou can choose one of the following options:
- Load Graph with All Properties: In this case, the complete graph with all its properties will be loaded into memory.
- Load Graph with Selected Properties: The slider will display the list of available vertex and edge properties for the graph. By default, all the properties are selected. You can choose to select (or deselect) specific vertex or edge properties that you wish to load into memory. Note that the properties that are unsupported by the graph server (PGX) will appear disabled.
To delete the graph. To convert a PGQL property graph into SQL graph. Note that this option is supported only if you are using an Autonomous Database instance with Oracle Database 23ai. Also, this action is available only for PGQL property graphs. See Convert a PGQL Property Graph to SQL Property Graph for more information.
This executes the desired action on the property graph. - Optionally, click the </> Query button if you wish
to query and validate the selected property graph in the Query Playground
page.
The following example shows running SQL graph queries on a SQL property graph in the SQL tab of the Query Playground page. Note that the SQL tab is displayed only for Autonomous Database based on Oracle Database 23ai.
The following example shows running PGQL graph queries on a PGQL property graph in the PGQL tab of the Query Playground page:
Also, note the following when using the Query Playground page:
CREATE PROPERTY GRAPH
andDROP PROPERTY GRAPH
statements are supported.SELECT
queries are supported, and theSELECT
query results can be visualized, if applicable.INSERT
andUPDATE
queries are not supported.- All queries are executed as the currently logged in user.
- The current query will be persisted in the browser's local storage once executed.
- You cannot run multiple statements or queries separated by semi-colon in the SQL tab. Only one SQL statement or query is allowed.