Direct Disconnect Statement
The direct disconnect statement enables you to leave the pass-through mode enabled by your previous direct connect.
If you use direct disconnect before committing an active local DBMS SQL transaction, Ingres Star commits the transaction and sends the commit to the local DBMS.
Direct disconnect does not close Ingres Star’s session with the local DBMS. Any state that you set up while directly connected remains in place and may cause side effects in Ingres Star’s session with the local DBMS. Therefore, you must reset any session parameters (such as set statements) established during direct connect mode before issuing the direct disconnect. For example, if you issue a set autocommit on statement during a direct connect session, you must issue a set autocommit off before you issue the direct disconnect.
Direct Disconnect Syntax
The direct disconnect statement has the following format:
direct disconnect
Example: Direct Connect and Direct Disconnect
To place an integrity on an Ingres Star-level table, use the direct connect statement to define the integrity at the local level since an Ingres Star-level table actually resides in a local database.
create table employee (name char(100),
dept integer, salary money)
with node=remote1, database=mydb;
commit;
direct connect with node=remote1,
database=mydb;
create integrity on employee is salary>0;
direct disconnect;
Last modified date: 08/14/2024