Managing Transactions in the RAI Console
The Console provides a list of transactions — queries or updates to the database, by login or account.
You can use the list of transactions to view a history of your transactions, view past query results, or identify, cancel, or get support on a lagging query.
To manage transactions, click the Transactions icon (the clock) on the left side of the Console.
The Transactions page opens:
For each transaction, the Transactions page lists information such as the database, engine, query, state, start/finish time, duration, and whether or not the transaction was read-only.
Transaction States
Transactions can be in one of four states:
| Status | Explanation |
|---|---|
| Created | Transaction has been issued but is not yet running. |
| Running | Transaction is currently running. |
| Completed | Transaction has run successfully. |
| Aborted | Transaction has been canceled by the user or aborted by the system. See Abort Reasons below for more details. |
Canceling a Transaction
While a transaction is running, you can cancel it by clicking Cancel in the far right-hand column. Canceled transactions will eventually move to an aborted state. Note that cancellation is best-effort: If a transaction happens to complete before the system processes the cancellation, it may move to a completed state.
Viewing All Database Transactions
By default, the Transactions page displays the last 100 transactions for only your login.
To view transactions for your entire account, click the Only My Transactions switch in the upper right-hand corner of the Transactions page so that it is in the Off position.
To switch back to only your transactions, click the Only My Transactions switch again so that it is in the On position.
Note: SDK OAuth credentials are shared across the entire account, not per-user, so the Only My Transactions toggle will only show transactions you initiated from the web Console UI.
Searching Transactions
You can search for transactions by entering text in the search box. Search conducts a fuzzy, client-side search on all columns.
Search returns only for transactions already displayed; it will not return results for earlier transactions.
Viewing Transaction Details
You can view detailed information on a transaction, which looks like this:
The transaction detail page displays the following information:
- Details on the transaction, such as the time it was created and its duration.
- The Rel code for the transaction.
- If applicable, the transaction’s results.
Transaction Detail Fields
| Field | Explanation |
|---|---|
| Id | Unique identifier for the transaction. Useful for communicating with RAI support. |
| Database | Database in which the transaction ran. |
| Engine | Engine on which the transaction ran. |
| State | Current state of the transaction: Created, Running, Completed, or Aborted. |
| Abort Reason | If transaction was aborted, reason why. |
| Created On | Time when the transaction was initiated. |
| Finished At | Time when the transaction completed. |
| Duration | Amount of time the transaction took to run. |
| Readonly | Whether or not the transaction inserted or deleted base relation data. |
| Format Version | For SDKs, version of SDK for purposes of data type encoding. Best practice is to use the latest version of the SDK. |
| User Agent | For SDKs: name of SDK. For Console: browser and hardware on which the transaction ran. |
| Tags | Displays metadata attached to a transaction via SDKs. For more information, contact support@relational.ai. |
Abort Reasons
| Abort Reason | Explanation |
|---|---|
| System Internal Error | System has experienced an error. |
| Cancelled | Transaction was canceled by user. |
| Engine Shutting Down | Engine was shut down before transaction could complete. |
| Invalid Request | Transaction resulted in invalid request to server. |
| Integrity Constraint Violation | Transaction cancelled because query violates an integrity constraint. See the Integrity Constraints concept guide for more details. In these cases, the transaction still shows results, so that you can debug the query. |