Firebird Releases


The second alpha of Firebird 3.0 is about to be released. Find more information at http://sourceforge.net/p/firebird/code/HEAD/tree/firebird/tags/T3_0_0_Alpha2/doc/WhatsNew

Firebird Project announces the first Alpha release of Firebird 3.0, the next major version of the Firebird relational database, which is now available for testing.

This Alpha release arrives with an early preview of the features and improvements currently under development by the Firebird development team, as well as with countless bugfixes. Our users are appreciated giving it a try and providing feedback to the development mailing list. Apparent bugs can be reported directly to the bugtracker.
Alpha releases are not encouraged for production usage or any other goals that require a stable system. They are, however, recommended for those users who want to help in identifying issues and bottlenecks thus allowing to progress faster through the Beta/RC stages towards the final release.

Please read the Release Notes carefully before installing and testing this Alpha release.

URL to build from is: http://svn.code.sf.net/p/firebird/code/firebird/tags/T3_0_0_Alpha1/.

Roadmap was also updated
http://www.firebirdsql.org/en/roadmap/

For testing you can use the pre alpha snapshots For Linux:
http://web.firebirdsql.org/downloads/snapshot_builds/linux/fb3.0/
and Windows:
http://web.firebirdsql.org/downloads/snapshot_builds/win/3.0/

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.3.

See http://www.firebirdsql.org/en/jdbc-driver/ for the downloadlinks.

The release is also available on maven:
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.3</version>

The artifactId depends on your target Java version: jaybird-jdk15, jaybird-jdk16 or jaybird-jdk17.

The following has been changed or fixed in Jaybird 2.2.3:

  • Fixed incorrect synchronization in native and embedded protocol (JNI) implementation for iscBlobInfo and iscSeekBlob (JDBC-300)
  • Fixed holdable ResultSet is closed on auto-commit (JDBC-304, JDBC-305)
  • Fixed table names missing or padded with spaces in Database view of IntelliJ IDEA (JDBC-308, IDEA-100786)
  • Fixed incorrect JDBC minor version reported under Java 7; this resulted in an incorrect column name (for Java 7) in the metadata of DatabaseMetaData.getColumns(…) (JDBC-309)
  • Added IOException to cause of GDSException with error 335544721; “Unable to complete network request to host “”” for further investigation (JDBC-306)

More details are available in the Jaybird 2.2.3 releasenotes.

Important Debian security fix is uploaded to sid http://packages.qa.debian.org/f/firebird2.5/news/20130318T154817Z.html

You can check Firebird 2.5/2.1 packages security status for this bug CVE-2013-2492 on this page

https://security-tracker.debian.org/tracker/CVE-2013-2492

New Firebird packages that fix security bug #9322 in Mageia are available for Mageia 2 and Cauldron

An important security fix for Firebird is pushed to Fedora and EPEL
Please update your servers.

Here is how the patch looks if you want to apply to other Linux distros

 

 

FDB release 1.0 is out:
http://pypi.python.org/pypi/fdb

Improvements:

- Removed dependency on presence of fbclient library at import time. This caused some confusion to new users when fdb install failed when Firebird was not (yet) installed.

Bugs Fixed:

http://tracker.firebirdsql.org/browse/PYFB-25

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.2.

See http://www.firebirdsql.org/en/jdbc-driver/ for the downloadlinks.

The release is also available on maven:
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.2</version>

The artifactId depends on your target Java version: jaybird-jdk15,
jaybird-jdk16 or jaybird-jdk17

The following has been changed or fixed in Jaybird 2.2.2:

  • Fixed: FBMaintenanceManager.listLimboTransactions() reports incorrect transaction id when the result contains multi-site transactions in limbo (JDBC-266)
  • Fixed: Calling PreparedStatement.setClob(int, Clob) with a non-Firebird Clob (eg like Hibernate does) or calling PreparedStatement.setClob(int, Reader) throws FBSQLException: “You can’t start before the beginning of the blob” (JDBC-281)
  • Fixed: Connection property types not properly processed from isc_dpb_types.properties (JDBC-284)
  • Fixed: JNI implementation of parameter buffer writes incorrect integers (JDBC-285, JDBC-286)
  • Changed: Throw SQLException when calling execute, executeQuery, executeUpdate and addBatch methods accepting a query string on a PreparedStatement or CallableStatement as required by JDBC 4.0 (JDBC-288)
    NOTE: Be aware that this change can break existing code if you depended on the old, non-standard behavior! With addBatch(String) the old behavior lead to a memory leak and unexpected results.
  • Fixed: LIKE escape character JDBC escape ({escape ‘<char>’}) doesn’t work (JDBC-290)
  • Added: Support for a connect timeout using connection property connectTimeout. This property can be specified in the JDBC URL or Properties object or on the DataSource. If the connectTimeout property is not specified, the general DriverManager property loginTimeout is used. The value is the timeout in seconds. (JDBC-295)
    For the Java wire protocol the connect timeout will detect unreachable hosts. In the JNI implementation (native protocol) the connect timeout works as the DPB item isc_dpb_connect_timeout which only works after connecting to the server for the op_accept phase of the protocol. This means that – for the native protocol – the connect timeout will not detect unreachable hosts within the timeout. As that might be unexpected, an SQLWarning is added to the connection if the property is specified with the native protocol.
  • As part of the connect timeout change, hostname handling (if the hostname is an IP-address) in the Java wire protocol was changed. This should not have an impact in recent Java versions, but on older Java versions (Java 5 up to update 5) this might result in a delay in connecting using an IP-address, if that address can’t be reverse-resolved to a hostname. Workaround is to add an entry for that IP-address to the /etc/hosts or %WINDIR%\System32\Drivers\etc\hosts file.

News via Mark Rotteveel tweet

I just released Jaybird 2.2.2 newsitem and maven artifacts should appear in a day or so

Update: NewsItem apeared on the main site also on FirebirdNews

Next Page »


This Firebird & Interbase WebRing site owned by Carlos H. Cantu .
[ Previous 5 Sites | Previous | Next | Next 5 Sites | Random Site | List Sites ]