IDataConn is deprecated and is provided for backward compatibility only. New applications should use the java.sql.Connection interface from the JDBC Core API.

IDataConn conn;

if((conn = createDataConn(0, GX_DA_DAD_DRIVERS.GX_DA_DRIVER_ODBC, 
"CATALOG", "CATALOG", "steve", "pass7878")) == null)

. . .

public int closeConn(
	int dwFlags)

dwFlags. Specify 0, or GX_DA_CLOSECONN_FLAGS.GX_DA_UNBIND_TRANS, which explicitly unbinds a physical connection from a transaction.

• Closing the database connection changes the state of the IDataConn object to closed.
• Close a database connection only after the AppLogic no longer needs it. A run-time error will occur if subsequent operations attempt to use a data connection object that has already been closed.

IDataConn conn;

if((conn = createDataConn(0, GX_DA_DAD_DRIVERS.GX_DA_DRIVER_ODBC, 
"CATALOG", "CATALOG", "steve", "pass7878")) == null)

{

   // Cannot connect - return error message

   result("Failed to connect to Catalog db");

   return null;

};

// Connected - return the data connection object

// used for subsequent operations on the database

return conn;

};

. . . perform database operations . . .

// Explicitly close the connection

int closeResult;

closeResult=conn.closeConn(0);

int createTrigger(
	String pTable,
	String pName,
	String pCondition,
	String pOptions,
	String pSQLBlock); 

pTable. The table on which the trigger is defined. You can specify the name of the owner as a prefix to the table name, for example, "jim.myTable".

pName. The name of the trigger object to create.

pCondition. The condition that determines whether or not the SQL procedure (defined in the pSQLBlock parameter) executes. For example, you can specify that the SQL procedure executes only if a column contains a specific value:

"FOR EACH ROW WHEN(city = 'San Francisco')"

pOptions. The row operations that determine when the trigger executes. For example, you can specify that the trigger be activated BEFORE or AFTER an INSERT, UPDATE, and/or DELETE operation:

"AFTER INSERT, UPDATE"

pSQLBlock. The definition of the SQL block to execute when the trigger goes into effect. Refer to your database documentation for information on the SQL block format.

• For specific information on supported trigger options and conditions, refer to the description of triggers in your database documentation.
• After creating a trigger, enable it by calling enableTrigger( ). The following are exceptions to the rule:

• Sybase does not support the enabling or disabling of triggers.
• Oracle automatically enables a trigger when the trigger is created; you can optionally call enableTrigger( ), but it will have no effect.

IDataConn conn;

conn = createDataConn(0, GX_DA_DAD_DRIVERS.GX_DA_DRIVER_ODBC,

  "personnelDB", "personnelDB", "sandra", "pass7878");

conn.createTrigger("employees", "ProcessNew", 

  "FOR EACH ROW WHEN(title='Director')",

  "AFTER INSERT", "[SQL instruction here]";

conn.enableTrigger("employees", "ProcessNew");

public int disableTrigger(
	String pTable,
	String pName);

pTable. The table in which the trigger is located.

pName. The name of the trigger to disable.

public int dropTrigger(
	String pTable,
	String pName);

pTable. The table on which the trigger is defined.

pName. The name of the trigger to remove.

public int enableTrigger(
	String pTable,
	String pName);

pTable. The table on which the trigger is defined.

pName. The name of the trigger to enable.

public IResultSet executeQuery(
	int dwFlags,
	IQuery pQuery,
	ITrans pTrans,
	IValList pProps)

dwFlags. Specifies flags used to execute this query.

• For synchronous operations, the default, specify zero or GX_DA_EXECUTEQUERY_FLAGS.GX_DA_EXEC_SYNC.
• For asynchronous operations, specify GX_DA_EXECUTEQUERY_FLAGS.GX_DA_EXEC_ASYNC.
• To activate result set buffering, specify GX_DA_EXECUTEQUERY_FLAGS.GX_DA_RS_BUFFERING.

(GX_DA_EXECUTEQUERY_FLAGS.GX_DA_EXEC_ASYNC | 
GX_DA_EXECUTEQUERY_FLAGS.GX_DA_RS_BUFFERING) 

pQuery. IQuery object that contains the flat query object to execute.

pTrans. ITrans object that contains the transaction to which this query applies, or null.

pProps. IValList object that contains query properties, or null for no properties. After instantiating an object of the IValList interface, set any of the following properties:

• RS_BUFFERING turns on result set buffering when set to "TRUE".
• RS_INIT_ROWS specifies the initial size of the buffer, in number of rows. If the result set size exceeds this setting, a fetchNext( ) call will return the error GX_DA_FETCHNEXT_RESULTS.GX_DA_BUFFER_EXCEEDED.
• RS_MAX_ROWS specifies the maximum number of rows for the buffer. If the result set size exceeds this setting, a fetchNext( ) call will return the error GX_DA_FETCHNEXT_RESULTS.GX_DA_BUFFER_EXCEEDED.
• RS_MAX_SIZE specifies the maximum number of bytes for the buffer.

• Before calling executeQuery( ), AppLogic must create a query by first calling createQuery( ) in the AppLogic class (deprecated) to create the IQuery object, then using methods in the IQuery interface (deprecated) to define the query.
• If the query is part of a transaction, before calling executeQuery( ), the AppLogic must first create the ITrans transaction object using createTrans( ) in the AppLogic class (deprecated), then begin the transaction using begin( ) in the ITrans interface (deprecated), and then specify the ITrans object as a parameter when calling executeQuery( ).

// Create the flat query object

IQuery qry=createQuery();



// Set up the query

qry.setTables("CTLcust");

qry.setFields("CustomerID, Customer");

qry.setWhere("Customer"+"="+String.valueOf(custId));



// Execute the query

IResultSet rs=conn.executeQuery(0, qry, null, null);

// Check for a non empty result

if((rs!=null)&&(rs.getRowNumber()>0))

	return result("Sorry, this user ("+

	firstName+" "+lastName+") already exists");

// Otherwise, process the result set

// Set up result set buffering for query

IValList props;

props = GX.CreateValList();

// Turn on result set buffering

props.setValString("RS_BUFFERING", "TRUE");

// Specify the maximum number of rows to buffer

props.setValInt("RS_MAX_ROWS", 50);

IQuery qry = createQuery();

. . . define query properties . . .

// Attempt to execute query with result set buffering

IResultSet rs = conn.executeQuery(0, qry, null, props);

public IValList getConnInfo()

public IValList getConnProps()

public int getDriver()

public ITable getTable(
	String szTable)

szTable. Name of the table to request. This can include the schema name, for example, "jim.myTable." Do not use patterns or wildcards.

• To change data in the table using methods in the ITable interface (deprecated) to insert, update, and delete rows.
• When the schema of a table is unknown, to obtain information about the table definition from the database catalog, such as table name, table columns, data connection, and so on.

• If the table name is unknown, use getTables( ) to retrieve an IValList of tables in the data source, then use methods in the IValList interface and the Val class to iterate through the table names obtained and determine which table to retrieve.
• To obtain additional information about individual columns, use the IColumn interface (deprecated).

ITable table = dbConn.getTable("CTLcust");

if(table==null) return result("Can't find the table: "+"CTLcust");

// Otherwise, process the table columns

int cCustId = table.getColumnOrdinal("CustomerID");

int cFirst = table.getColumnOrdinal("FirstName");

. . .

public IValList getTables(
	String szQualifier,
	String szOwner,
	String szTable)

szQualifier. Specify null. Driver-dependent.

szOwner. Specify null, or a schema name, which returns tables for that schema.

szTable. Table or view name with wildcards, or null for all tables. Wildcards must be in the format supported by the data source. For example, you can use search patterns using the following characters:

• underscore (_) for single characters
• percent sign (%) for any sequence of zero or more characters

• The AppLogic must be logged in with sufficient privileges to obtain a list of tables from the database. For more information, see your database server documentation.
• The AppLogic must specify a valid table name, view name, or name pattern. Aliases and synonyms are not supported for security reasons.

public ICallableStmt prepareCall(
	int dwFlags,
	IQuery pQuery,
	ITrans pTrans,
	IValList pProps);

dwFlags. Specify 0.

pQuery. The IQuery object that contains the call to a stored procedure. The stored procedure call should have been specified with the setSQL( ) method in the IQuery interface.

pTrans. ITrans object that contains the transaction associated with this callable statement, or null for no transaction. This same ITrans object must then be passed to the execute( ) method of the ICallableStmt interface.

pProps. Specify null.

• Before calling prepareCall( ), the AppLogic must create a query by first calling createQuery( ) in the AppLogic class (deprecated) to create the IQuery object, then using the setSQL( ) method in the IQuery interface (deprecated) to define the call to a stored procedure.
• When accessing a stored procedure on Sybase or MS SQL Server, input parameter names must be prefixed with the ampersand (&) character, for example, &param1. Other database drivers accept the ampersand, as well as, the colon (:) character. For all database drivers, input/output and output parameter names are prefixed with the colon (:) character, for example, :param2.

// Create the database connection.

IDataConn conn_rtest = createDataConn(0, 
GX_DA_DAD_DRIVERS.GX_DA_DRIVER_DEFAULT, 

/* Datasource name */ "ksample", 

/* Database name   */ "", 

/* userName        */ "kdemo",

/* password        */ "kdemo");



//Write command to call stored procedure

String theProc = "{call myProc1(&p1, :p2)}";

IQuery myquery;

myquery = createQuery();

myquery.setSQL(theProc);



//Prepare the callable statement for execution

ICallableStmt myStmt;

myStmt = conn_rtest.prepareCall(0, myquery, null, null);



// Set parameters and run the callable statement

public IPreparedQuery prepareQuery(
	int dwFlags,
	IQuery pQuery,
	ITrans pTrans,
	IValList pProps)

dwFlags. Specify 0.

pQuery. IQuery object that contains the query or statement to execute.

pTrans. ITrans object that contains the transaction to which this query applies, or null. This same object must then be passed to the execute( ) method of the IPreparedQuery interface.

pProps. Specify null.

// Create the data connection

IDataConn conn;

conn = createDataConn(0, GX_DA_DAD_DRIVERS.GX_DA_DRIVER_DEFAULT, 
"Orders", "Orders", "user", "password");



// Create the flat query and prepared query objects

IQuery qry = createQuery();

IPreparedQuery pqry;

IValList params;

params = GX.CreateValList();



// Set up the INSERT statement

qry.setSQL("INSERT INTO TABLE Products (ProductName, QuantityPerUnit) 
VALUES (:name, :quant)");



// Prepare the flat query

pqry = conn.prepareQuery(0, qry, null, null);



// Specify a set of query parameters, then execute

params.setValString(":name","Chicken Dumplings");

params.setValString(":quant", "48 packages");

IResultSet rs1 = pqry.execute(0, params, null, null);

. . . process rs1. . .



// Specify different set of query parameters, then execute

params.setValString(":name", "Rice Noodles");

params.setValString(":quant", "96 packages");

IResultSet rs2 = pqry.execute(0, params, null, null);

. . . process rs2. . .

public int setConnProps(
	IValList pProps)

pProps. A pointer to the IValList object that contains the connection properties to set in the registry. Use the following defined key names for the connection properties: