PHP 7.0.14 available with PDO_Firebird fixes

The PHP development team announces the immediate availability of PHP 7.0.14.
This is a security release. Several security bugs were fixed in this
release.

All PHP 7.0 users are encouraged to upgrade to this version.

For source downloads of PHP 7.0.14 please visit our downloads page:
http://www.php.net/downloads.php

Windows binaries can be found on http://windows.php.net/download/

The list of changes is recorded in the ChangeLog:
http://www.php.net/ChangeLog-7.php#7.0.14

Regards,
Anatol Belski and Ferenc Kovacs

ps: Firebird related change

PDO_Firebird:

  • Fixed bug #73087, #61183, #71494 (Memory corruption in bindParam).

IBX2 is now available with full support for the Firebird 3 API

MWA Software is pleased to announce the release of IBX2 for Lazarus. This is formally a pre-release. Although the software has been put through more extensive testing that any previous release of IBX for Lazarus, there are nevertheless considerable changes to the codebase and a period of in service experience is needed before IBX2 should be considered for production use. User reports, both positive and negative, are encouraged.

IBX2 is available for download from http://www.mwasoftware.co.uk/ibx2

The IBX2 headlines are:

  • Full support for both the Firebird 3 API and the legacy Firebird API.
  • Support for Firebird Arrays including a new Data Aware control derived from a TCustomStringGrid.
  • Reduced RAM footprint.
  • Support for embedded SQL statement execution.
  • Extensive testing has been performed with emphasis on avoiding memory leaks and to ensure that the performance is at least as good as previous versions.
  • Further bug fixes (see changelog).

IBX2 requires a minimum of FPC 3.0.0 and Lazarus 1.6.0.

The original IBX code has been split into two packages: the main IBX package which provides the non-visual components, and a new fbintf package (see separate announcement). The fbintf package provides a common interface for the Firebird 3 API and the legacy Firebird API and is the means by which embedded SQL statement execution is supported. The fbintf package may also be used on its own and has the potential to provide a common Firebird API to all FPC database applications.

IBX2 includes much improved documentation. There is a 108 page user guide for IBX itself and an 89 page user guide to the Firebird Pascal API provide by the fbintf package. There are also 15 example programs included in the package.

IBX2 is intended to be backwards compatible and most user applications should re-compile with no issues. However, there are differences and the user guide includes a section on upgrading to IBX2.

Third Bug Hunting Session for LibreOffice 5.3

bhs_5-3-0-beta2_largeLibreOffice 5.3 will be announced at the end of January 2017, with a large number of new features which are summarized on the release notes page: https://wiki.documentfoundation.org/ReleaseNotes/5.3.

In order to find, report and triage bugs, the LibreOffice QA team is organizing a third bug hunting session on Friday, December 9, and Saturday, December 10, 2016.

Here is Firebird 3.0 upgrade notice in LibreOffice Base 5.3.

Also detailed migration notes for older ODB files are in the Wiki.

Firebird 3 by default in LibreOffice 5.4 (Base)

Lots of missing features & big bugs were fixed recently .
All of the blockers that were initially mentioned on tracking bug are now fixed.

Lionel mentioned that he added a few more blockers that needs to be fixed until Firebird will be switched by default in LibreOffice Base :

I went over
https://bugs.documentfoundation.org/buglist.cgi?quicksearch=firebird

and added a few open bugs to the blocker bug

https://bugs.documentfoundation.org/51780

based on their description (and NEW instead of UNCONFIRMED status)
only, without reading the bug log in great detail.

Tamás Bunth (Wastack) agreed that 6 months time frame is more than enough to fix bugs that will appear

I agree, it would be reasonable to wait a half year. Until that we can
fix the already found and the upcoming bugs, solve the backward
incompatibility. Even if those can be solved quickly we can upgrade to
the c++ API.

Another issue is importing old hsqldb databases without java installed


It requires making a read-only parser for the HSQLDB “cached” table
data format in another language than Java. Most definitely possible,
the format may even be better documented than “read the source code”.


			
		
1 38 39 40 41 42 294