Mark Rotteveel migrated the first documents to asciidoc

Mark Rotteveel and documentation team migrated the first documents to asciidoc

– Docbuilding Howto
https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docbuildhowto/firebird-docbuilding-howto.html
– Docwriting Guide
https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html

ps: Since May/June 2020, the Firebird documentation project has switched to AsciiDoc for its documentation. This section gives a short overview how AsciiDoc is used by the project.

Jaybird 3.0.9 released

Jaybird 3.0.9 has been released. This release contains the following changes:

  • Fixed: changes to the transaction configuration (transaction parameter buffer configuration) of one connection are no longer propagated to other connections with the same connection properties (JDBC-386)
  • New feature: Firebird 4 data type bind configuration support (JDBC-603)
  • New feature: Jaybird now supports UTF-8 URL encoding for connection properties in the JDBC url. (JDBC-604)
  • Fixed: When updating a row through an updatable result set, selected but not updated blob fields were set to NULL (JDBC-623)

Jaybird 3.0 supports Firebird 2.0 and higher, on Java 7, 8, 11 and 14. Basic Java 9 and higher compatibility is provided through the Java 8 version of the driver.

See also:

Django 2.2 driver for Firebird 3

RED SOFT has added support of Firebird 3 into the Django 2.2 framework.

RED SOFT developer Vasily Yashkov made a pull request which recently has been accepted. Find details and main changes here.

The new version of the driver was successfully tested with Django 2.2.10/2.2.11 and Firebird 3/RedDatabase 3.

If you use Django with Firebird 2.5 or less please try to migrate your database to Firebird 3.0 and test new version of the driver. Now you can install it manually as described in the instruction but follow the news and wait the next release soon.

New Firebird driver for Python

As Pavel Cisar promised at Firebird Conference in Berlin, the Firebird has brand
new DB API 2.0 driver for Python. It’s part of modernization campaign
that shakes off the legacy that goes back to KInterbasDB and Firebird 2.0.

Please note, that his new driver requires Firebird 3+ and Python 3.8+.
This “high” base line was chosen deliberately, to use all new features
available from latest Firebird & Python releases without constraints and
limits that backward compatibility would require. Internally, the driver
uses new client API based on interfaces introduced by Firebird 3. This
new API has many limits raised (like statement sizes, blob sizes etc.)
or completely lifted (like number of databases participating in
distributed transaction), and provides access to new Firebird features
(like scrollable cursors).

The initial release (v0.5.0) supports all key driver features you know
from FDB (passes all tests for FDB features), with next exceptions:

Missing parts:
– distributed transactions (will appear in next version)
– FDB extensions like schema, monitoring tables and log parsers. These
modules will be developer later, and released as separate package.
– documentation

New features in comparison to FDB:
– scrollable cursors
– type hints everywhere
– new FB client API instead old one
– enhanced Enums and Flags classes instead isc_* constants
– better and more rich support for Firebird services

The driver has also much cleaner structure and namespaces, and less core
code than FDB, and although it was not measured yet, it should also
perform better. However, the driver API is not 100% backward compatible
(with FDB).

Right now, the new driver is available only from project’s GitHib at
https://github.com/FirebirdSQL/python3-driver

Changes to Newsgroups

Since the end of last year, Yahoo! has stopped hosting news groups as forums.  As you may noticed, the web interfaces and all message histories have been removed.  Messages are now delivered only as email and there is no control to prevent SPAM and nuisance contributors.
We have the moves of firebird-java, firebird-support and firebird-general under way so far.  You should subscribe to the Google list and post all messages there from now on. For the link to a list’s Google address, please visit https://firebirdsql.org/en/mailing-lists/
Firebird-php is moving also, but its new home currently needs work.

RedExpert: free open source tool for Firebird administration from RedSoft

RedSoft, Platinum Sponsor of Firebird Foundation and contributor of Firebird Project development, has introduced the new major version of the free open-source multi-platform tool for administration and development of Firebird databases: RedExpert v2020.04.1.

The new version introduces:a test data generator, database object dependencies, and many other improvements and bug fixes.
Download here RedExpert installation and binaries.

Join RedExpert development
If you like RedExpert as a tool and as an idea of a free multi-platform high-quality tool for Firebird, and if you have experience as a Java developer or tester, or simply as advanced Firebird user, please join the development effort: RedExpert sources are available in GitHub, please submit your pull-requests there, and send your feedback, bug reports, suggestions, etc to Issues section on GitHub.

Firebird discussion lists moving to GoogleGroups

Since Yahoo is slowly killing its discussion lists, some of the Firebird “official” discussion lists are being moved to GoogleGroups.

Firebird-support seems to be the first one:

Hello Firebird-support members,

The firebird-support list is moving to Google Groups. The new location is https://groups.google.com/d/forum/firebird-support

Unfortunately we cannot migrate the current Yahoo! subscribers, and you will need to resubscribe yourself, in one of two ways:

(1) If you have a Google account, log in to Google, go to the group’s home page https://groups.google.com/forum/#!forum/firebird-support;context-place=overview), Click the link labelled ‘Join this group’ and follow instructions there.

(2) Without a Google account, you can apply to join by emailing this address using the email account you want to use for communicating with the group:

firebird-support+subscribe@googlegroups.com

You should receive a confirmation email. Respond as directed to complete. (this does not require a Google account).

For posting to the list you can use firebird-support@googlegroups.com

Note, if you are subscribed to more than one Firebird-related Yahoo! group, your will need to go trough a similar process for each of your groups.

Helen Borrie for Firebird Project
1 26 27 28 29 30 199