Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Isolate/extract metadata ResultSet behavior [JDBC310] #356

Closed
firebird-automations opened this issue May 8, 2013 · 5 comments
Closed

Isolate/extract metadata ResultSet behavior [JDBC310] #356

firebird-automations opened this issue May 8, 2013 · 5 comments

Comments

@firebird-automations
Copy link

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.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 2.3 [ 10440 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 3.1 [ 10441 ]

Fix Version: Jaybird 3.0 [ 10440 ] =>

@firebird-automations
Copy link
Author

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 ] =>

@mrotteveel
Copy link
Member

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.

@mrotteveel
Copy link
Member

With recent changes to how database metadata is handled, this has become less of an issue.

@mrotteveel mrotteveel closed this as not planned Won't fix, can't repro, duplicate, stale Jan 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants