jaybird
jaybird copied to clipboard
FirebirdSQL
Isolate/extract metadata ResultSet behavior [JDBC310]
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.
Modified by: @mrotteveel
Fix Version: Jaybird 3.1 [ 10441 ]
Fix Version: Jaybird 3.0 [ 10440 ] =>
Modified by: @mrotteveel
Fix Version: Jaybird 5 [ 10871 ]
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.
Fix Version: Jaybird 4 [ 10441 ] =>
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.
With recent changes to how database metadata is handled, this has become less of an issue.