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
Firebird 4 support [JDBC466] #505
Comments
Modified by: @mrotteveelFix Version: Jaybird 3.1 [ 10441 ] description: Identify the changes and new features in Firebird 4 and add support (through subtasks). => Identify the changes and new features in Firebird 4 and add support (through subtasks). Tentatively scheduled for Jaybird 3.1. Some things may move to 3.0, otherwise might be delayed further. |
Modified by: @mrotteveeldescription: Identify the changes and new features in Firebird 4 and add support (through subtasks). Tentatively scheduled for Jaybird 3.1. Some things may move to 3.0, otherwise might be delayed further. => Identify the changes and new features in Firebird 4 and add support (through subtasks). Tentatively scheduled for Jaybird 4. Some things may move to 3.0, otherwise might be delayed further. |
Modified by: @mrotteveelFix Version: Jaybird 4.0.2 [ 10950 ] Fix Version: Jaybird 4.0.1 [ 10921 ] => |
Modified by: @mrotteveelFix Version: Jaybird 4.0.3 [ 10981 ] Fix Version: Jaybird 4.0.2 [ 10950 ] => |
Modified by: @mrotteveelFix Version: Jaybird 4.0.4 [ 10991 ] Fix Version: Jaybird 4.0.3 [ 10981 ] => |
This was a parent issue in Jira, no longer relevant, so closing it. |
Submitted by: @mrotteveel
Jira_subtask_outward JDBC467
Jira_subtask_outward JDBC468
Jira_subtask_outward JDBC506
Jira_subtask_outward JDBC516
Jira_subtask_outward JDBC540
Jira_subtask_outward JDBC564
Jira_subtask_outward JDBC570
Jira_subtask_outward JDBC583
Jira_subtask_outward JDBC591
Jira_subtask_outward JDBC595
Jira_subtask_outward JDBC596
Jira_subtask_outward JDBC624
Identify the changes and new features in Firebird 4 and add support (through subtasks).
Tentatively scheduled for Jaybird 4. Some things may move to 3.0, otherwise might be delayed further.
The text was updated successfully, but these errors were encountered: