Blogroll


Firebird driver become Ole Db .Net Provider

We are pleased to announce the second release candidate of our .NET Data Provider for interaction with Firebird and Interbase via IBProvider. By now, we have implemented all the functionality of System.Data.OleDb.

If you want to transfer your .NET projects for FB/IB to the new level of functionality and quality, we recommend you to start using «LCPI .NET Data Provider for OLE DB».

Just look of this DDEX screenshot:

You can get more screenshots and download Ole Db .Net Provider for access to any Interbase or any Firebird database from ADO.Net here: OleDb .Net driver for Firebird >>>

More info here.

You can get the bits from NuGet FirebirdSql.Data.FirebirdClient and EntityFramework.Firebird.

I’m pleased to announce new version of .NET provider. You can read more at http://blog.cincura.net/233471-ado-net-provider-4-5-0-0-for-firebird-is-ready/.

ADO.NET provider 4.2.0.0 for Firebird is ready and you can find more at http://blog.cincura.net/233462-ado-net-provider-4-2-0-0-for-firebird-is-ready/.

ADO.NET provider for Firebird 4.1.5.0 is ready

ADO.NET provider for Firebird 4.1.0.0 is ready

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

ADO.NET provider for Firebird 4.0.0.0 is ready

Nigel Weeks created a demo for an assignment (for his Paramedic Practice degree) for a small fictional town’s health clinic, some appointment rooms, and some remote health professionals that are employed a few days a week (You can check it online also download the source code : Firebird SQL , PHP , webrtc, Ubuntu Server):

Naturally, I used the tools I know and love: PHP, FirebirdSQL, a splash of CSS, and a dollop of HTML.

Its feature set:

-Client management, current and outdated contact information(historical support)
-Bookings to see specialists, and notes system to go with the consultancy
-Booking screen with calendar for each specialist, and automatic blocking out for longer appointments.
-Daily run sheets for specialists (so they can see their appointment load in the morning)
-Payment status reports on appointments
-Reports on Specialist’s booking loads, and booking trends for hour of the day
-Outstanding account reports
-A WebRTC TeleHealth system for remote client and specialist consultancy and more. Oh yes, role-based access control(rudimentary)

With the impending implementation of Firebird as a backend for LibreOffice Base, to replace HSQLDB, I re-ran the tests of converging and cyclic cascades that were previously carried out for other databases.

These tests were carried out using Firebird 2.5 running on Ubuntu Server 12.04.2

 

Next Page »


This Firebird & Interbase WebRing site owned by Carlos H. Cantu .
[ Previous 5 Sites | Previous | Next | Next 5 Sites | Random Site | List Sites ]