Each operation in a database service invokes a stored procedure or SQL statement in a database. Database operations are created and edited with the Database Operation Wizard.
The inputs and outputs of a database operation exist in the service that contains the operation as an XML schema. The following must be considered when adding an operation for database services:
XSD types to JDBC
The JDBC input parameter data types are automatically mapped to XSD based on the type you define when you create the operation. For example, if a stored procedure has an input parameter defined as a VARCHAR, the input parameter must be an xsd:string. If the input parameter data type is incompatible with the expected JDBC type, an exception is thrown.
See JDBC Data Type Mapping to XSD.
Statement Types
Strongly Typed Database Service Operations
Strongly typed services are strict types with formatting that matches the types. They are used because strongly typed services look more like other services; for example, result sets and columns can be given more meaningful names. They also allow easier mapping.
Generically Typed Database Service Operations
Generic database service operations define inputs and outputs in a generic way so all inputs and outputs look the same for all services. They are used because mapping to input and output generically needs to be done one time for all generic operations. For example, generic types would provide an advantage when you encounter variations in the format of a stored procedure, the number of results sets returned by a stored procedure, or the result set columns based on SQL fragments used within a SQL statement.
Note: The "strongly typed" vs. "generically typed" option is available for selection when new database services are created; therefore, this feature is only available in the new database service wizard.
If your SQL statement contains SQL fragment parameters, be sure to change the value in the column titled SQL Fragment to true for that parameter.