I am using the standard SelectSQL to retrieve data from a oracle DB as follows:
Expression Column Type JDBC Type Output Field Sort Order
COLUMN1 VARCHAR2(5) VARCHAR COLUMN1
COLUMN2 VARCHAR2(5) VARCHAR COLUMN2
COLUMN3 VARCHAR2(5) VARCHAR COLUMN3 Ascend
COLUMN4 VARCHAR2(5) VARCHAR COLUMN4

When this JDBC adapter was created the Input/Output tab matched the same order as the columns chosen on the Select Tab and this extracted document list is then mapped to another pipeline variable as a referenced document list. The orginal document follows the same order (COLUMN1,2,3,4) as the above referenced JDBC adapter.

I would now like to modify the sort order of the SelectSQL to include
COLUMN1 in Ascending order, but COLUMN3 still be the primary (first) sort order. Since there is no precendence that can be set I could only do the following:
Expression Column Type JDBC Type Output Field Sort Order
COLUMN2 VARCHAR2(5) VARCHAR COLUMN2
COLUMN3 VARCHAR2(5) VARCHAR COLUMN3 Ascend
COLUMN1 VARCHAR2(5) VARCHAR COLUMN1 Ascend
COLUMN4 VARCHAR2(5) VARCHAR COLUMN4

Whenever I make this change it has no effect on the input/output tab column order as they remain
COLUMN1
COLUMN2
COLUMN3
COLUMN4

However whenever I run the JDBC adapter either standalone or thru the calling flow service the data is returned properly but in the order of the select tab. This dosn’t seem to have a problem as even the data being mapped to the outbound document (even though a different order) still flows though the processing downstream correctly.

Is there a better way to handle these type of changes other than using CustomSQL? I would like to keep the JDBC and outbound document synchronized and the same order but I don’t know if it really matters.

“…but I don’t know if it really matters.”

It doesn’t matter.