6 Loading a SQL Property Graph into the Graph Server (PGX)

You can load a full SQL property graph or a subgraph into memory in the graph server (PGX).

Note:

Ensure that you drop the graph when it is no longer in use to release the graph server (PGX) memory. See Deleting a Graph for more information.

The following topics describe the various ways to load a SQL property graph into the graph server (PGX).

• Loading a SQL Property Graph Using the readGraphByName API
  You can load a SQL property graph into the graph server (PGX) by calling the readGraphByName API on a PgxSession object.
• Loading a Subgraph Using PGQL Queries
  You can create an in-memory subgraph from a SQL property graph using the PgSqlSubgraphReader API.
• Expanding a Subgraph
  You can expand an in-memory subgraph by loading graph data from a SQL property graph into memory, and merging it with the current subgraph.
• Handling Vertex and Edge Identifiers in the Graph Server (PGX)
  The Oracle Database maintains globally unique identifiers in JSON format.
• Mapping Oracle Database Types to PGX Types
  Learn how the input Oracle database types are mapped to its corresponding PGX types, when a graph from the database is loaded into the graph server (PGX).
• Privileges to Load a SQL Property Graph
  Learn about the privileges required to load a SQL property graph into the graph server(PGX).
• Restriction on Key Types
  Learn about the vertex and edge keys restrictions when loading a full or partial SQL property graph into memory in the graph server (PGX).
• Loading SQL Property Graphs with Unsupported Key Types
  If existing keys in a SQL graph cannot be loaded into the graph server (PGX), then generated keys maintained by the database may be used instead.