You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in the parent issue, the current behavior of metadata ResultSets lead to some problems. Change the existing fix so casts to VARCHAR(31) are no longer necessary. The current conditional behavior for metadata ResultSet could be isolated to a separate subclass of FBResultSet, or maybe in a Strategy.
The text was updated successfully, but these errors were encountered:
description: As described in the parent issue, the current behavior of metadata ResultSets lead to some problems. Change the existing fix so casts to VARCHAR(31) are no longer necessary. The current conditional behavior for metadata ResultSet could be isolated to a separate subclass of FBResultSet, or maybe in a Strategy.
The main objective of this task is to research and implement a better solution in 2.3
=>
As described in the parent issue, the current behavior of metadata ResultSets lead to some problems. Change the existing fix so casts to VARCHAR(31) are no longer necessary. The current conditional behavior for metadata ResultSet could be isolated to a separate subclass of FBResultSet, or maybe in a Strategy.
I'm making some changes to address this partially, and remove most of those casts. This issue to refactor metadata result sets to a separate class has been unscheduled, as there is no urgent reason to do this.
Submitted by: @mrotteveel
Jira_subtask_inward JDBC308
As described in the parent issue, the current behavior of metadata ResultSets lead to some problems. Change the existing fix so casts to VARCHAR(31) are no longer necessary. The current conditional behavior for metadata ResultSet could be isolated to a separate subclass of FBResultSet, or maybe in a Strategy.
The text was updated successfully, but these errors were encountered: