New issue of EmberWings magazine published

EmberWings is a quarterly PDF magazine about Firebird published by IBPhoenix.

Beyond technical articles, instructions and tips, it contains interviews with noteworthy individuals, an overview of Firebird’s development, information from the Firebird community, evaluations of compelling products, and a touch of thematic humor. All of this presented in a streamlined format with an aesthetically pleasing print-friendly layout.

The magazine is available in IBPhoenix store for free on a pay-what-you-want basis, with half of the proceeds going to the Firebird Foundation. The remaining half is used to finance the publication of the magazine.

This issue has 70 pages.

Jaybird 5.0.5 released

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:

Real-time Firebird – Monitor for Firebird – Server 2.5 / 3.0 / 4.0 / 5.0

We are pleased to present the new version 2 of the Firebird Monitor with “Trace and Audit”.

We are currently offering a 10% discount on the purchase of a license until the end of June 2024. The coupon code is “Discount10”.

With “Trace and Audit”, they are able to record and evaluate every single event in the database.

Visit our homepage and download the demo version.

https://fbm.gksoft.ch

Database Workbench 6.5.0 released

Upscene Productions is proud to announce the availability of the next release of the popular multi-DBMS development tool:

” Database Workbench 6.5.0″

Changes in recent releases:

  • Firebird 5 support
  • MySQL 8.3 support
  • PostgreSQL 16.x support
  • SQLite module introduced for full SQLite support, read only support in Pro and Enterprise editions without this module

Database Workbench 6 comes in 3 different editions with different pricing models, there’s always a version that suits you!

Perl extension DBD::Firebird version 1.38 is released

Perl extension DBD::Firebird version 1.38 is released with quite a few changes if you compare with previous announcement , here are a few from the ChangeLog: add support for Firebird’s BOOLEAN data type , add support for disabling database-level triggers

Revision history for Perl extension DBD::Firebird.
1.38 [2024-05-21]
 * fix syntax error boolean fall back implementation (thanks to Robert Scheck)
 * add support for disabling database-level triggers (gh#53)
1.37 [2024-05-20]
 * fall back to sv_setiv when sv_setbool is not available (gh#58)
1.36 [2024-05-19]
 * fix problems with Perl before 5.36 and Firebird before 3.0
   (gh#56 and gh#57)
1.35 [2024-05-15]
 * ib2sql_type: ignore nullability bit
 * map Firebird's 64-bit integer type to SQL_BIGINT
 * add support for Firebird's BOOLEAN data type
 * fix a couple of compiler warnings

Release of IBProvider v5.37

We are glad to present a new release of IBProvider — v5.37. This update contains a lot of internal changes and improvements. All the changes have been tested more than one time, so this release is ready for use in your projects. Please update your copy of IBProvider with this version. If you work with Firebird, please use «fb.direct» mode. Thanks.

https://www.ibprovider.com/eng/news/n_240518.html

Build of error message in built-in Firebird client

  • The current release of IBProvider adds the new initialization property ctype_system that allows to point a codepage of operation system where a connected database server is working. This information will help IBProvider process the DBMS system errors
  • Provider uses a connection charset for translating server error messages into UNICODE

Work with ICU

  • ICU 63.1 (FB4). A suppression of translation error between code pages is disabled now (FB:CORE-8108)
  • A processing of ucnv_open function return code is corrected

Common changes

  • vc16 binaries are compiled with C++20
  • vc15 binaries use a built-in thread pool based on the source code of the external thread pool of vc16/vc17 assemblies (source code unification)
  • The information content of the error message “unsupported database server version” is improved
  • The internal instrumental C++ library was refactored

With Best Regards, IBProvider Team.

Firebird-Export

Export a Firebird database to CSV, JSON or other formats is a Open Source project to export a Firebird database, show a summary of the database table names, field names, field data types, and index columns. Optionally extract and save table data to a directory, in CSV/JSON (or potentially in any other format), as well any other binary files from blobs.

A subset of the tables and fields can be specified (in python) and the number of records returned can be limited for testing purposes. Output data can be combined or into one or saved in individual files named after the tables.

1 2 3 4 5 6