Jaybird 6.0.0-beta-1 is now available for testing. You can download the distribution zip from Jaybird 6.0.0-beta-1 (GitHub).

IMPORTANT

This version is provided for testing purposes only. We'd appreciate your feedback, but we'd like to emphasize that this version is not intended for production.

What's new

The major changes and new features in Jaybird 6 are:

• Minimum supported Java version is Java 17.
  See Java support for more information.
• Minimum supported Firebird version is Firebird 3.0.
  See Firebird support for more information.
• The pure Java protocol — by default — no longer connects to Firebird 2.5 and older, as those versions are not supported.
  See Pure Java will not connect to unsupported Firebird versions by default for more information.
• The native and embedded protocols have been moved to a separate artifact, jaybird-native.
  See NATIVE and EMBEDDED support moved to a separate artifact for more information.
• OOREMOTE (OpenOffice/LibreOffice protocol) removed
• Modularization of Jaybird
• Connection property createDatabaseIfNotExist
• Report actual process ID (pid)
• Logging facade removed
• Support for ChaCha64 wire encryption
• Opt-in feature for package information in DatabaseMetaData
• Asynchronous fetching
• Blob performance improvements
• Support for executing transaction management statements
• Configurable buffer sizes for the wire protocol
• Broken connection detection for event manager
• Connection property to specify native library path
• Rewritten client info properties support
• TIMESTAMP fields now accept LocalDate and LocalTime
• ResultSet in auto-commit no longer closed after last row
• Changes to behaviour of updatable scrollable result sets
• …​ and Other fixes and changes

Upgrading from Jaybird 5 should be straightforward, but please make sure to read Compatibility changes before using Jaybird 6. If you’re using Jaybird with the native or embedded connections, you will need to make some additional changes. See also Upgrading from Jaybird 5 to Jaybird 6.

Bug reports about undocumented changes in behavior are appreciated. Feedback can be sent to the Firebird-java mailing list or reported on the issue tracker https://github.com/FirebirdSQL/jaybird/issues.

See also the full Jaybird 6.0.0-beta-1 release notes.

Maven

The release is also available on Maven:

groupId: org.firebirdsql.jdbc
artifactId: jaybird
version: 6.0.0-beta-1

If you use the native or embedded protocol, you need to add the jaybird-native dependency:

groupId: org.firebirdsql.jdbc
artifactId: jaybird-native
version: 6.0.0-beta-1

For ChaCha64 wire encryption support, add the chacha64-plugin dependency:

groupId: org.firebirdsql.jdbc
artifactId: chacha64-plugin
version: 6.0.0-beta-1

We have received numerous emails related to the "3 top challenges with Firebird" campaign. These include questions, problems, and suggestions from users.

In this video, Vlad Khorsun, a core developer of Firebird, and Alexey Kovyazin, the former President of the Firebird Foundation and current Firebird Foundation Programs Coordinator, address the first set of these user inquiries.

Prague, 17th Oct 2024 – After more than two decades of operation from Australia, the Firebird Foundation is excited to announce a major transformation. A new organization of the same name has been established, now operating from the Czech Republic, within the European Union. This shift marks a significant step in strengthening the Foundation's ties to Project Firebird, one of the leading open-source relational database systems.

The new Firebird Foundation has been set up with a closer connection to Project Firebird, which enables a more efficient and focused approach to supporting its development. This change promises a range of advantages for Firebird users, especially for those who contribute to the ongoing development of the database.

“We are excited about this transition,” said Alexey Kovyazin, former President of the Firebird Foundation in Australia. “Having the Firebird Foundation so closely linked to the core project team will streamline our ability to address the needs of Firebird users and drive the database’s progress more effectively. This will benefit the entire Firebird community, from individual developers to large enterprises relying on Firebird as their database solution.”

As the world continues to face economic and technical challenges, ongoing support from the community is more crucial than ever. Firebird’s global user base relies on this database for mission-critical operations, and ensuring its continued development and innovation is key. The new Firebird Foundation, with its European location, is well-positioned to offer faster, more tailored responses to the evolving needs of users.

Support the Future of Firebird

The Firebird Foundation remains committed to supporting its community, and this change enhances its ability to do so. Users are encouraged to get involved by supporting the project through donations or sponsorships. Contributions directly impact Firebird's development, allowing the project to remain a leading, cost-effective solution for developers and businesses worldwide.

“We want to assure our community that Firebird remains strong,” said Pavel Císař, vice-president and secretary of new Firebird Foundation. “Our users and supporters are the backbone of this project, and their continued contributions are more important than ever in these difficult times. By supporting the Firebird Foundation, you are ensuring the future of this essential open-source database.”

For more information about the new Firebird Foundation and how to contribute, visit [https://www.firebirdsql.org/en/firebird-foundation].

About Firebird

Firebird is a powerful, open-source relational database management system used worldwide by developers, enterprises, and individuals. It offers robust features and scalability while maintaining a small footprint, making it a preferred choice for a wide range of applications.

Media Contact:
Alexey Kovyazin, [email protected]