Using Jaybird with Firebird 3.0 alpha 1

Mark Rotteveel wrote on Firebird Java list :

I have started a page on the Jaybird wiki on using Jaybird with Firebird

3.0 alpha 1:

http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=tip:firebird30a1

It lists know problems, compatibility issues and workarounds between
Jaybird 2.2.x and earlier and Firebird 3 (alpha 1).

It is a work in progress, but I hope to have all the basics listed by
Sunday. If you miss something, or something doesn’t work for you with
Firebird 3, let me know.

Mark

Firebird 3.0 Alpha 1 release is available for testing

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.

Jaybird 2.2.4 snapshot with basic Java 8 / JDBC 4.2 support

Mark Rotteveel wrote about new Firebird JDBC driver snapshot:

I just created a snapshot version of Jaybird 2.2.4 with basic Java 8 /
JDBC 4.2 support. It is available for download from:
https://sourceforge.net/projects/firebird/files/firebird-jca-jdbc-driver/2.2.4-snapshot-jdk18/

This snapshot provides basic support for Java 8 by overriding the new
default interface methods added with a slightly more sane default. Most
of the changes in Java 8 are about supporting large update counts (>
Integer.MAX_VALUE) and the new SQLType interface.

For the large update counts Jaybird simply delegates to the methods
returning int values.

The Statement.setLargeMaxRows(long) method will set the max to 0 (no
maximum) if a value larger than Integer.MAX_VALUE is supplied.

The SQLType methods will delegate to the methods accepting an int
sqlType parameter with the value obtained from getVendorTypeNumber()
without further validation or checking. The exception to this are the
ResultSet.updateObject(…) methods which don’t have an equivalent
accepting an integer type parameter. In that case it is delegated to the
equivalent method without type support.

The snapshot is also available on maven in the Sonatype OSS snapshot
repository: https://oss.sonatype.org/content/repositories/snapshots

Firebird Driver and Embedded version merged into LibreOffice git master

Changes to libreoffice and firebird driver can be seen in the git log

And here is announcement :

Firebird has now been integrated into LibreOffice master!

It now builds on Mac and Windows in addition to Linux. (I’ve only tested on Linux but will be testing/fixing as necessary on Mac/Windows this week.)

The database driver itself is almost unusable at the moment as I’ve been refactoring various things to do with transaction control and execution of statements. More and more functionality should be appearing in the course of this week, making the driver more usable .

Odb with embedded firebird db

Firebird .ODB

 

 

Firebird .Net Provider is moving to Git/Github

Jiri Cincura wrote about his issues with SourceForge and SVN also his idea to move
to a better system : git/github:

Maybe you remember the thread “Releasing more often???“. Yeah and
nothing happened. 🙂 Because there was not a strong protest, I think
it’s something we all ‘d like to have.

I was lately really pissed of by SF’s SVN. If you worked with it, not
just committing, I think just using it, you can feel my pain. So first
part of the improving I’d like to offer moving to Git on GitHub. I’m
not a fan of GitHub (I like BitBucket, if somebody asks), but it’s a
de-facto standard in OSS.

With this we will also gain benefits like downloading the sources
packed, downloadig specific version etc.

Also I’d like to release *only* on NuGet and latest version for latest
framework as MSI (on website). The rest can be downloaded/extracted
from NuGet. We now support just .NET 3.5 SP1 and later, thus at least
VS2010 and so NuGet is available to everybody. And even that, you can
grab NuGet.exe and download from command line, if you want (i.e.
you’re hard-core developer using Notepad and csc only :)). Both these
with higher cadence, shorter release loop as mentioned in previous
thread.

Maybe I’m too optimistic, so please let me know what you think and
what you think is going not work. 😉

1 86 87 88 89 90 298