Hi, Recently there came up a requirement from user (ref. JIRA-1355), when the user was attempting DAS.createCommand(sql) in Oracle. As of today, in RDB DAS, user can specify ResultDescriptor using external Config File containing Commands. But there is no provision for user to pass ResultDescriptor for a Command, when it is created as above (dynamic - without Config File). As, for Oracle and some other databases, when database meta data is not sufficient, DAS requires user to supply ResultDescriptor as a substitute. For taking care of such situations, DAS needs to expose Command.set/getResultDescriptors(List <ResultDescriptor>).
One rule to be adhered when using this API will be sequencing of ResultDescriptors in the input List.The sequence in the List <ResultDescriptor> has to be in sync with the sequence of parameters in "sql". With this, I guess it will be a really useful and handy functionality, that RDB DAS needs to consider. Thoughts? Regards, Amita