News
July 25, 2024

Thank you for your valuable feedback! I’ve received numerous emails with suggestions, questions, and descriptions of issues that Firebird users are encountering.

I’ll be addressing these questions in a video meeting in the beginning of August (there are many questions!), where I’ll share our responses and discuss upcoming features and plans. Stay tuned, and thank you for supporting Firebird!

Regards,
Alexey Kovyazin
President OF Firebird Foundation

Thank you for your valuable feedback! I’ve received numerous emails with suggestions, questions, and descriptions of issues that Firebird users are encountering.

I’ll be addressing these questions in a video meeting in the beginning of August (there are many questions!), where I’ll share our responses and discuss upcoming features and plans. Stay tuned, and thank you for supporting Firebird!

Regards,
Alexey Kovyazin
President OF Firebird Foundation

July 15, 2024

Dear Firebird Community,

As president of the Firebird Foundation, I'm reaching out to tap into the wealth of experience and knowledge within our user base. We're constantly striving to improve Firebird, and your feedback is crucial in guiding our efforts.

I'd like to ask for your input on a critical question:

What are the 3 biggest problems with Firebird that impact you?

Whether you're developing software with Firebird or using it as the backbone of your business operations, we want to hear about the challenges you face.

No issue is too big or too small – we're interested in everything from technical limitations to documentation gaps, from performance bottlenecks to ecosystem concerns.

Your real-world experiences are invaluable to us. By sharing your top three issues, you'll help us prioritize our development efforts and focus on the areas that matter most to our community.

Please send your thoughts to [email protected].

Feel free to elaborate on your points if you'd like – the more context we have, the better we can understand and address the issues.

Even if you will send just 3 lines, it will be also useful.

Thank you in advance for your time and insights. Your feedback will play a crucial role in shaping the future of Firebird.

Best regards,

Alexey Kovyazin

President, Firebird Foundation

Email to answer: [email protected]

Dear Firebird Community,

As president of the Firebird Foundation, I'm reaching out to tap into the wealth of experience and knowledge within our user base. We're constantly striving to improve Firebird, and your feedback is crucial in guiding our efforts.

I'd like to ask for your input on a critical question:

What are the 3 biggest problems with Firebird that impact you?

Whether you're developing software with Firebird or using it as the backbone of your business operations, we want to hear about the challenges you face.

No issue is too big or too small – we're interested in everything from technical limitations to documentation gaps, from performance bottlenecks to ecosystem concerns.

Your real-world experiences are invaluable to us. By sharing your top three issues, you'll help us prioritize our development efforts and focus on the areas that matter most to our community.

Please send your thoughts to [email protected].

Feel free to elaborate on your points if you'd like – the more context we have, the better we can understand and address the issues.

Even if you will send just 3 lines, it will be also useful.

Thank you in advance for your time and insights. Your feedback will play a crucial role in shaping the future of Firebird.

Best regards,

Alexey Kovyazin

President, Firebird Foundation

Email to answer: [email protected]

June 14, 2024

We are happy to announce the release of Jaybird 5.0.5.

The following has been fixed since Jaybird 5.0.4:

  • Fixed: FBResultSetMetaData.getPrecision would always estimate the precision of NUMERIC or DECIMAL columns instead of obtaining the actual precision if the column position was 71 or higher (#731)

  • Optimized the query to retrieve extended field info for ResultSetMetaData.getPrecision to only retrieve columns of type NUMERIC or DECIMAL (#732)

  • Fixed: PreparedStatement.executeBatch() of statement without parameters throws “Statement used in batch must have parameters [SQLState:07001, ISC error code:335545186]” on Firebird 4.0 or higher (#788)

  • New feature: ResultSetMetaData.isAutoIncrement(int) reports true for identity columns if Jaybird can identify the underlying table and column (#793)

  • New feature: Boolean connection property extendedMetadata (default true) to disable querying of extended metadata for getPrecision(int) and isAutoIncrement(int) of ResultSetMetaData (#795)

  • Improvement: The FILTER_CONDITION of DatabaseMetaData.getIndexInfo is populated for Firebird 5.0 partial indices (#797)

  • Fixed: ResultSet.isBeforeFirst() and ResultSet.isAfterLast() should always report false for an empty result set (#807)

  • Improvement: Statement.getResultSet no longer throws a SQLException with message “Only one result set at a time/statement” if the current result set has already been returned by executeQuery or a previous call to getResultSet (#762)

  • Improvement: Updated JNA dependency to version 5.14.0 (#810)

Jaybird 5 supports Firebird 2.5 and higher, on Java 8, 11, 17, 21, and 22 (support for Java 11 and higher using the Java 11 version of the driver).

See also:

We are happy to announce the release of Jaybird 5.0.5.

The following has been fixed since Jaybird 5.0.4:

  • Fixed: FBResultSetMetaData.getPrecision would always estimate the precision of NUMERIC or DECIMAL columns instead of obtaining the actual precision if the column position was 71 or higher (#731)

  • Optimized the query to retrieve extended field info for ResultSetMetaData.getPrecision to only retrieve columns of type NUMERIC or DECIMAL (#732)

  • Fixed: PreparedStatement.executeBatch() of statement without parameters throws “Statement used in batch must have parameters [SQLState:07001, ISC error code:335545186]” on Firebird 4.0 or higher (#788)

  • New feature: ResultSetMetaData.isAutoIncrement(int) reports true for identity columns if Jaybird can identify the underlying table and column (#793)

  • New feature: Boolean connection property extendedMetadata (default true) to disable querying of extended metadata for getPrecision(int) and isAutoIncrement(int) of ResultSetMetaData (#795)

  • Improvement: The FILTER_CONDITION of DatabaseMetaData.getIndexInfo is populated for Firebird 5.0 partial indices (#797)

  • Fixed: ResultSet.isBeforeFirst() and ResultSet.isAfterLast() should always report false for an empty result set (#807)

  • Improvement: Statement.getResultSet no longer throws a SQLException with message “Only one result set at a time/statement” if the current result set has already been returned by executeQuery or a previous call to getResultSet (#762)

  • Improvement: Updated JNA dependency to version 5.14.0 (#810)

Jaybird 5 supports Firebird 2.5 and higher, on Java 8, 11, 17, 21, and 22 (support for Java 11 and higher using the Java 11 version of the driver).

See also:

More News
Case Studies