Below is a design idea, please refer to,
The expansion in the future, we can enrich the clover types, then add a cursor type, DataFieldMetadata.CURSOR_FIELD, this type can not achieve the specific details of the nodes DB_EXECUTE outParameters inParameters and attribute data types through the metadata file transfer,
This design means good.
In classes12.jar in OracleTypes.java the constants defined below
public static final int CURSOR = -10;
SQLUtil.java edit documents, modify the jetelType2Sql,
public static int jetelType2sql(char jetelType) {
…
case DataFieldMetadata.CURSOR_FIELD:
return -10;
…
}
dbexe_DELIMITED_DATA_READER_0_0__MetaData.fmt
<?xml version="1.0" encoding="gb2312"?>
dbexe_DELIMITED_DATA_WRITER_0_0__MetaData.fmt
<?xml version="1.0" encoding="gb2312"?>
oracle return cursor result graph(outParameters,outputFields):
<Node id=“DB_EXECUTE_0” type=“DB_EXECUTE” printStatements=“Y” dbConnection=“testorcl” inTransaction=“N” sqlStatementDelimiter=“;” callStatement=“Y” inParameters=“1:=$Field0;2:=$Field1;3:=$Field2” outParameters=“4:=cursor” outputFields=“c1;c2;c3” >
{call p_hw1(?,?,?,?)}
oracle return parameters graph (outParameters,outputFields):
<Node id=“DB_EXECUTE_0” type=“DB_EXECUTE” printStatements=“Y” dbConnection=“testorcl” inTransaction=“N” sqlStatementDelimiter=“;” callStatement=“Y” inParameters=“1:=$Field0;2:=$Field1;3:=$Field2” outParameters=“4:=integer;5:=string;6:=date” outputFields=“c1;c2;c3” >
{call p_hw1(?,?,?,?,?,?)}
ms-sql return record result graph (outputFields):
<Node id=“DB_EXECUTE_0” type=“DB_EXECUTE” printStatements=“Y” dbConnection=“testmssql” inTransaction=“N” sqlStatementDelimiter=“;” callStatement=“Y” inParameters=“1:=$Field0;2:=$Field1;3:=$Field2” outputFields=“c1;c2;c3” >
{call p_hw1(?,?,?)}
OutParameters attributes is imported clover type, rather than through clover fields name analytical types.
Storage process is the result of a return of property through outputFields