Bug #8025
Persistence API improvements
0%
History
#1 Updated by Constantin Asofiei 6 months ago
Eric, customers need to access the result set metadata for the ScrollableResults> resultSet = connection.executeSQLQuery(sql,new Object[]{});
result.
Is it acceptable to add a ScrollableResults.getResultSet
to expose the JDBC internals?
#2 Updated by Constantin Asofiei 6 months ago
- Subject changed from add ScrollableResults.getResultSet to Persistence API improvements
Another part which is requested by customers to be improved: executeSQLBatch
to return an int[]
array with the result (number of updated records) for each statement.
#3 Updated by Alexandru Lungu 6 months ago
Constantin Asofiei wrote:
Eric, customers need to access the result set metadata for the
ScrollableResults> resultSet = connection.executeSQLQuery(sql,new Object[]{});
result.Is it acceptable to add a
ScrollableResults.getResultSet
to expose the JDBC internals?
Just a small remark on this one: maybe we can have ScrollableResults.getMetadata
instead. My point is that some of the FWD API (especially #6720 which is almost ready) may depend on not moving the result-set (i.e. doing .next
) outside the ScrollableResults
. Also, mind the .close
and .update*
methods we certainly do not want to expose.