Category: General news

Firebird related news

Jaybird 2.2.4 released

Leave a comment

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

This release contains the following fixes:

  • Fixed: Exceptions during statement preparation leave connection and transaction open after explicit close (JDBC-311)
  • Fixed batch update (or insert) with blob set through setBinaryStream() sets empty blob for all but the first batch entry (JDBC-312)
  • Fixed incomplete checks of database, transaction, statement and blob handle validity before continuing with actions. These incomplete checks could lead to unexpected exceptions (for example a NullPointerException in iscDatabaseInfo) (JDBC-313)
  • Fixed error when setting connection charset equal to "file.encoding" java property (JDBC-314)
  • Fixed connection character set not correctly set when specifying the Java connection characterset (charSet or localEncoding property)  (JDBC-315)
  • Fixed incorrect lengths and/or radix reported by getTypeInfo and getColumns metadata (JDBC-317, JDBC-318)
  • Initial Java 8 / JDBC 4.2 support (JDBC-319)
  • Firebird 3 BOOLEAN type support, see Support for Firebird 3 BOOLEAN type in the release notes for more details (JDBC-321)
  • Added fallback of loading GDSFactoryPlugin implementations to prevent NullPointerException in Hibernate reverse engineering wizard in NetBeans (JDBC-325)
  • Fixed: Jaybird should specify dialect 3 in dpb when no explicit dialect was set (JDBC-327)
  • Fixed: several DatabaseMetaData methods defined by JDBC to only accept the actual table name also accepted a LIKE-pattern or empty string or null. This was changed to conform to JDBC. This change can break applications that relied on the incorrect behavior (JDBC-331)
    Affected methods are: getPrimaryKeys, getBestRowIdentifier, getImportedKeys, getExportedKeys and getCrossReference. As part of this change getIndexInfo now handles names in the wrong case slightly different.
    Jaybird 3.0 will further modify and restrict the pattern matching and case sensitivity of metadata methods. See Future changes to Jaybird in the release notes for more details.

Downloads available from JDBC driver section on the Firebird website.

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.4</version>

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

LibreOffice 4.2 International Bug Hunting Session

Leave a comment

The Document Foundation announces LibreOffice 4.2 International Bug Hunting Session, which will start on December 6th and will end on December 8th. During the three days, volunteers from all over the world will test the beta of LibreOffice 4.2 to find bugs and regressions.

LibreOffice 4.2 will be released at the end of January 2014, with a large number of new features (https://wiki.documentfoundation.org/ReleaseNotes/4.2) and loads of fixed bugs. The community is working to make this major release the finest in the history of the free office suite.

In order to join the bug hunting session, volunteers should download LibreOffice 4.2 Beta 2, available fromhttp://www.libreoffice.org/download/pre-releases/.

Mentors will be available at least from 08:00 UTC to 22:00 UTC, and will be reachable through IRC (irc://chat.freenode.net/libreoffice-qa) and the QA mailing list.

Other information on LibreOffice 4.2 International Bug Hunting Session are available at https://wiki.documentfoundation.org/BugHunting_Session_4.2.0.

What is interesting for Firebird is finding/fixing bugs related to Libreoffice Base and Firebird

  • NEW TECHNOLOGY PREVIEW FEATURE: Firebird SQL connector for LibreOffice Base (Andrzej Hunt). When creating a new Database, select Firebird Embedded in the drop down menu (you have to first enable the Experimental features in Tools ▸ Options ▸ LibreOffice ▸Advanced). This allows creation of databases that perform many times faster than the previous built-in HSQLDB 1.8, avoiding the C++-to-Java overhead inherent in using HSQLDB. We plan to phase HSQLDB out over the next few releases, and provide a smooth migration path to Firebird. Connecting to modern HSQLDB 2.x external databases remains available through HSQLDB’s native interface, namely JDBC.

 

FirebirdDB.png

Jaybird 2.3 will become Jaybird 3.0

Leave a comment

Mark Rotteveel announced :
As Jaybird 2.3 is going to be a big change from Jaybird 2.2, I have
decided to renumber the version to Jaybird 3.0.

Changes planned for Jaybird 2.3 are now planned for Jaybird 3.0. Changes
planned for Jaybird 3.0 are now planned for Jaybird 3.1 (but might get
into Jaybird 3.0).

Some of the major changes include a new Type 4 (wire protocol)
implementation to be able to support new features in the wire protocols
(especially for Firebird 3*), and probably also in the Type 2 (native)
implementation. The behavior and compatibility of Jaybird and the
interpretation of the JDBC specification might (will) also change for
some cases and I think a new major version is needed to indicate this,
as I expect that this new version will not be a drop-in replacement in
all cases.

There is no date set for the release of Jaybird 3.0, work is progressing
but slowly and the changes made for the new wire protocol implementation
will cascade through the entire driver once I replace the existing
implementation.

Once the new wire protocol implementation is in place I will start
releasing snapshots for testing.

Development of Jaybird 2.2.x will continue at least until the release of
Jaybird 3.0. If necessary new features will be implemented and bugs will
continue to be fixed. For example Firebird 3 BOOLEAN type and (basic)
Java 8/JDBC 4.2 support will be added in Jaybird 2.2.4.

I have planned to release Jaybird 2.2.4 at the end of this month.

*: Actual implementation for the Firebird 3 authentication and
encryption protocol (SRP) is not yet planned for Jaybird 3.0.

ANN: FB TraceManager V3.0.2 has been released!

Leave a comment
FBTM_V3_48x48 Upscene Productions is excited to officially release FB TraceManager V3.0.2!


Ever wondered if garbage collection might be guilty when one and the same statement shows dramatic different execution time on the same data volume? We have the answer.

This release exposes user-friendly Firebird Garbage Collection information at statement-level in parsed trace data and in the per-database monitoring tables integration.

More information on V3.0.2 is available here:
http://www.upscene.com/displaynews.php?item=20131025

Don’t forget our 15% autumn discount: HERFST13

More information on the product is available in the FB TraceManager section on our website, including an edition comparison sheet, webcasts etc.:
http://www.upscene.com/go/?go=fbtm

1 … 104 105 106 107 108 … 200