Table Of Contents

Database Transaction (Connection) (G Dataflow)

Last Modified: February 27, 2020

Begins, commits, or rolls back a database operation performed by a connection object.

connector_pane_image
datatype_icon

connection reference

Reference to an ADO Connection object. Connection objects represent a connection with a data source, including methods to open and close a connection with a database, which database to connect with, and the level of isolation for database transactions.

datatype_icon

operation

Action you want to perform.

Name Description
begin Starts a transaction.
commit Records a transaction to the database.
rollback Discards changes made and restores the previous state of a database entry.

Default: begin

datatype_icon

isolation level

Degree to which transactions are visible to other users interacting with a database.

spd-note-note
Note

You only need to set the isolation level if other database transactions might be pending.

Name Description
chaos Transactions can overwrite each other.
read uncommitted You cannot see uncommitted records from another transaction. Dirty reads, non-repeatable reads, and phantom reads are all possible.
read committed You cannot see changes made by other transactions until they are committed. Dirty reads are not possible, but non-repeatable reads and phantom reads are.
repeatable read You cannot see any changes in records without requerying the database. Dirty reads and non-repeatable reads are not possible, but phantom reads are possible.
serializable The transaction occurs in complete isolation. Dirty reads, non-repeatable reads, and phantom reads are not possible.

Default: chaos

datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

connection reference out

Reference to an ADO Connection object. Connection objects represent a connection with a data source, including methods to open and close a connection with a database, which database to connect with, and the level of isolation for database transactions.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

Web Server: Not supported in VIs that run in a web application


Recently Viewed Topics