1.0

Description
The supported isolation levels in SQLFire are NONE, READ COMMITTED, and READ UNCOMMITTED.
The READ UNCOMMITTED level is implicitly upgraded to READ COMMITTED.
Isolation level NONE indicates no transactional behavior. The RESET clause corresponds to the NONE isolation
level.
Understanding the Data Consistency Model on page 135 and Using Distributed Transactions in Your Applications
on page 137 provide details about non-transactional and transactional behavior in SQLFire.
This statement behaves identically to the JDBC java.sql.Connection.setTransactionIsolation method and commits
the current transaction if isolation level has changed.
Example
sqlf(PEERCLIENT)> set ISOLATION READ COMMITTED;
0 rows inserted/updated/deleted
sqlf(PEERCLIENT)> VALUES CURRENT ISOLATION;
1
----
CS
1 row selected
SET SCHEMA
Set or change the default schema for a connection's session.
Syntax
SET [CURRENT] SCHEMA [=]
{ schema-name |
USER | ? | '<string-constant>' }
Description
The SET SCHEMA statement sets or changes the default schema for a connection's session to the provided
schema. This is then used as the schema for all statements issued from the connection that do not explicitly
specify a schema name. The SET SCHEMA statement is not transactional and does not affect commit or rollback
in any manner.
The USER clause above denotes the current user and causes the current schema to be set to the name of the
current user, else if no current user is defined then it defaults to the inbuilt APP schema.
? is a dynamic parameter specification that can be used in prepared statements that can be executed with different
schema values after a prepare.
Example
-- below are equivalent assuming a TRADE schema
SET SCHEMA TRADE;
SET SCHEMA trade;
SET CURRENT SCHEMA = trade;
SET CURRENT SCHEMA ”TRADE”; –- quoted identifier
–- lower case won't be found
SET SCHEMA = 'trade'
-- this sets the default schema to the current user id
SET CURRENT SCHEMA USER
487
SQL Language Reference