Project

General

Profile

Bug #8025

Persistence API improvements

Added by Constantin Asofiei over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Constantin Asofiei over 2 years 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 over 2 years 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 over 2 years 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.

Also available in: Atom PDF