After establishing the connection, you are ready to use methods on the Connection object to send requests from the application to operate the database.
If you are familiar with GQL (Graph Query Language) or UQL (Ultipa Query Language), you can execute queries using the gql() or uql() method. For more information, refer to the following:
The driver also provides the following dedicated methods for key database operations:
- Graph
- Schema and Property
- Data Insertion
- Query Acceleration
- HDC Graph and Algorithm
- Process and Job
- Access Control
- Data Export
- Server Statistics
Request Configuration
Requests to read the database are configured using RequestConfig, while those to write the database use InsertRequestConfig.
RequestConfig
The RequestConfig class includes the following attributes:
Attribute |
Type |
Default |
Description |
|---|---|---|---|
graph |
str | / | Name of the graph to use. If not specified, the graph defined in UltipaConfig.defaultGraph will be used. |
timeout |
int | / | Request timeout threshold (in second). |
host |
str | / | Specifies a host in a database cluster to execute the request. |
thread |
int | / | Number of threads for the request. |
timezone |
str | / | Name of the timezone, e.g., Europe/Paris. Defaults to the local timezone if not specified. |
timezoneOffset |
str | / | The offset from UTC, e.g., +2, +08, -0530, -02:00. When both timezone and timezoneOffset are provided, timezoneOffset takes precedence. |
InsertRequestConfig
The InsertRequestConfig class includes all attributes of the RequestConfig class, along with the following:
Attributes |
Type |
Default |
Description |
|---|---|---|---|
insertType |
Ultipa.InsertType |
NORMAL |
The insertion mode. Supports NORMAL, UPSERT, and OVERWRITE. |
silent |
bool | True |
Whether to return the _id or _uuid of the operated nodes or edges. Sets to Ture to not return, and False to return. |