ResultSetHandle and column definition lists #146
Comments
jcflack
added a commit
that referenced
this issue
Mar 23, 2018
A function declared to return RECORD or SETOF RECORD is required by SQL to be followed by a column definition list in any query using it. If the function returns SETOF RECORD using ResultSetHandle, there is a possibility that one or more corresponding columns in the definition list and the ResultSet offered by ResultSetHandle differ in type. Let the type be cast automatically, just as it would be when using ResultSetProvider and storing each value into the output ResultSet. Also convert the SetOfRecordTest example to an annotation-style example and add an SQLAction that tests it. Addresses issue #146.
jcflack
added a commit
that referenced
this issue
Mar 23, 2018
Expand the API docs to explain the interaction with the calling query's column definition list when a function is declared to return SETOF RECORD. Except for the type-casting behavior change in ResultSetHandle for issue #146, this is simply an exercise in documenting what currently happens.
|
Closing with release of 1.5.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a function is declared to return
RECORDorSETOF RECORD, SQL requires it to be followed by a column definition list when used in a query. If the function returnsSETOF RECORDusing theResultSetHandleinterface, it is possible that the column definition list specifies different types for one or more columns than theResultSetbeing supplied toResultSetHandle. In that case, the appropriate casts should happen, just as they would when usingResultSetProviderand storing the values into the outputResultSet.The text was updated successfully, but these errors were encountered: