Changing Default Transaction Behavior

To prevent updates to database content, explicitly start a transaction and specify that it is read only: START TRANSACTION READ ONLY (see START TRANSACTION). This starts an explicit transaction (see About Implicit and Explicit Transactions ) which will suspend the AUTOCOMMIT setting. This setting affects only the newly started transaction.

To change default autocommit behavior, specify SET AUTOCOMMIT OFF (See SET). When autocommit behavior is disabled and there is no START TRANSACTION statement, then execution of a statement implicitly starts a transaction. This transaction remains open until a COMMIT or ROLLBACK statement is executed (see COMMIT, ROLLBACK). Autocommit remains disabled unless there is a SET AUTOCOMMIT ON statement or the connection closes.

To change the default transaction isolation level, specify SET ISOLATION LEVEL isolation_level. The new setting is in effect with the start of the next transaction and stays in effect unless the level is reset with another SET command or the connection closes. See Supported Transaction Isolation Levels for a description of each transaction isolation level that NuoDB supports.
Another way to set the default transaction isolation level is to specify the isolation connection property when you open a connection. For example:

nuosql test@localhost --user dba --password dba --connection-property isolation=read_committed