Commands cancellation support in Firebird 2.5 and Interbase 6.5

 CREATE OR ALTER PROCEDURE SP_EXEC_DUMMY_COUNTER (n integer) AS BEGIN WHILE(N>0)DO BEGIN N=N-1; END END 

 [Test(Description = "Sample - Command.Cancel")] public void CancelCommand() { using (OleDbConnection con = ConnectionProvider.CreateConnection()) { con.Open(); OleDbTransaction trans = con.BeginTransaction(); cmd.CommandText = "exec SP_EXEC_DUMMY_COUNTER(5000000)"; // call cmd.ExecuteScalar using BackgroundWorker class BackgroundWorker bw = new BackgroundWorker(); bw.DoWork += delegate(object sender, DoWorkEventArgs e) { OleDbCommand cmd1 = e.Argument as OleDbCommand; Console.WriteLine("begin call"); cmd1.ExecuteScalar(); Console.WriteLine("end call"); }; bw.RunWorkerAsync(cmd); //Cancel command after 500 miliseconds System.Threading.Thread.Sleep(500); cmd.Cancel(); // waiting while cancel perform while (bw.IsBusy) { System.Threading.Thread.Sleep(500); } trans.Commit(); } } 

Support of new data type SQL_NULL in Firebird 2.5

 select count(*) from PROJECT where :par_null is NULL 

 dim cn, cmd, rs set cn = wscript.createobject("adodb.connection") call cn.open("Provider=LCPI.IBProvider.3;Password=masterkey;" & _ "Persist Security Info=True;User ID=sysdba; " & _ "Location=localhost:EMPLOYEE.FDB; dbclient_library=fbclient.dll") cn.BeginTrans WScript.Echo "IB Base=" & cn.Properties("IB Base").Value WScript.Echo "IB Client Version=" & cn.Properties("IB Client Version").Value WScript.Echo "Provider Version =" & cn.Properties("Provider Version").Value set cmd = WScript.Createobject("adodb.command") cmd.activeconnection = cn cmd.CommandText = "select count(*) from PROJECT where :par_null is NULL" cmd("par_null").Value = null set rs=cmd.Execute WScript.Echo cstr(rs(0)) cn.CommitTrans cn.Close 

 [Test(Description = "Sample - 'is NULL' operator")] public void ExecIsNullCommand() { using (OleDbConnection con = ConnectionProvider.CreateConnection()) { con.Open(); OleDbTransaction trans = con.BeginTransaction(); OleDbCommand cmd = new OleDbCommand("select (*) from PROJECT where ? is NULL", con, trans); cmd.Parameters.AddWithValue("", null); // if cmd parameter is null then command will return count result Assert.IsTrue((int)cmd.ExecuteScalar() > 0); trans.Commit(); } } 

Access to BLOB fields from ADOExpress (dbGo) bug was fixed

New implementation of result sets cache

• Asynchronous writing (in a separate stream) into own swap file has been implemented.
• Writing into a temporary file has been optimized.

Finally

New Option of working with TIME type via MS SQL Linked Server

Enhanced self-descriptiveness of error messages when working with temporary files.

Firebird and Interbase users implementing IBProvider drivers in their work last year were the first to take advantage of 64-bit applications.

We have produced two more drivers in addition to 64-bit IBProvider v3: IBProvider v2 and IBProvider v1.

Firebird, Interbase and 64-bit MS SQL Linked Server

Due to 64-bit IBProvider v2 driver, 16 versions of Firebird and Interbase are now available for recording on 64-bit Windows OS via MS SQL Linked Server.

64-bit updatable rowsets in ADO

In addition to MS SQL Linked Server, there are many libraries and utilities that support updatable rowsets technology implemented only in IBProvider v2. One of such libraries is ADO library.

64-bit support in ADO and WHS allows to develop 64-bit automation scripts in VBScript language. For example:

• Firebird/Interbase database automated administration scripts;
• scripts for building reports, eporting to Office, XML, sending reports via email;
• database backup, recovery, and replication scripts;
• customizable business logic scripts in 64-bit applications;
• etc.

Using IBProvider v2 on 64-bit platforms

For IBProvider v2 to work on 64-bit platforms, you need to have 64-bit Firebird 2.1 or Firebird 2.5 client installed on the computer. You will need to rename client’s DLL from fbclient.dll into gds32.dll and copy it to system32 directory. You can also choose this option while installing Firebird client via the installer. You can download Firebird 2.1 and Firebird 2.5 here: Firebird download .

Raising stability of drivers

Insignificant errors have been fixed in the new version, including the error in KEYCOLUMN description of IColumnsRowset interface.

With IBProvider drivers, writing of applications for Firebird and Interbase will become an easy and fascinating task. We have made provision for the most difficult and will gladly share our technologies with you .

Improved support of DDEX (Data Designer Extensibility) when working with Firebird and Interbase

IBProvider RC4 has the new option of stored procedures calling in Visual Studio 2008 style via ODBC escape sequences . This innovation allows to create queries and TableAdapters based on stored procedures.

Data Designer Extensibility: an example of accessing: Firebird and Interbase :

Optimized working with named parameters in SQL query text:

• Fewer limitations for multiple use of same named parameter in SQL query text
• New algorithm for choosing named parameter data type.
• Some errors of named parameters procession detected via profound testing by exhaustive method have been eliminated.

Metadata schemes and column descriptions (IColumnsRowset) support user encoding

Metadata schemes and IColumnRowset interface now consider user charset . This allows working with metadata in set encoding.

What comes next?

We continuously improve IBProvider and present new options for users with each new release. IBProvider Release Candidate 4 is the last RC of the third version.

We are planning complete substitution of IBProvider v2 functionality in the next IBProvider v3 Release:

• ability to work with updatable rowsets;
• support of data recording via Microsoft SQL Server Linked Server ;

Currently IBProvider v2 is the only provider that allows to update data in Firebird and Interbase Linked server. Other drivers allow only data reading from source.

IBProvider v3 RC4 is the result of 4-year innovations in data processing. It has implemented a lot of solutions and technologies, which make it completely different from other access components:

• Controllable charsets processor;
• SQL-parser with ODBC Escape Sequences support;
• Support of 16 Firebird and Interbase versions, including Firebird 2.5 and Interbase 2009;
• Automatic configuring for database server;
• Ability to work on 64-bit platforms;

Combination of these two drivers will give our clients another competitive advantage for quick development of quality Firebird and Interbase applications.

Download IBProvider Professional Edition (64/32 bit)

New IBProvider v.3.0.0.6600 RC3

• All the detected problems that prevented comprehensive work with Firebird and Interbase from UNICODE applications have been eliminated.
• Supports charset markers in SQL queries.
• Supports exclusions processing when working with Interbase and Firebird via ADODB.
• Supports working with database object names containing national symbols for connections with NONE charset.
• Enhanced work with metadata schemes when working with database via NONE charset.
• Advanced testing allowed detection and elimination of errors.
• ISO8859_15 charset support.

IBProvider has implemented the unique support of your database text data and presents very simple but flexible provider setting scheme to meet specific requirements of the client.

Detailed information on encoding processor setting: Firebird and Interbase charsets .

Charset markers in query text

IBProvider v3 have learned to process SQL queries containing charset markers.

Charset markers allow to transform individual text fields into specified encoding. They are used at data transfer to server. Example of a query with markers:

 insert into TEST_TABLE values(_unicode_fss'unicode_text', _win1251'ðóññêèé òåêñò') 

• 'unicode_text' will be transferred to server in UNICODE_FSS charset.
• 'ðóññêèé òåêñò' will be transformed into WIN1251 encoding.

Processing of exclusions when working with Interbase and Firebird via ADODB

After the new scheme of working with exclusions had been implemented in the latest releases, processing of errors was not supported at working with Firebird and Interbase via ADODB. This was due to undocumented interface code-named IDBPrimaryError, which has been successfully implemented in the new release.

Support of working with database object names containing national symbols for connections with NONE charset

When connecting to Interbase or Firebird database without charset specification, object names in double quotes in a SQL query will be transformed into UNICODE_FSS charset. This ensures correct work with objects, which names contain national symbols (not ASCII), for example, Russian letters. For example:

Select “ÑÒÎËÁÅÖ1” from “ÒÀÁËÈÖÀ1” 

Download IBProvider Professional Edition (64/32 bit)

Changes in IBProvider v2 [build 2.6.06.2688]

• Addition of UTF-8 charset support
• Loading of charset information for COLUMN and PROCEDURE_PARAMETERS metadata schemes from system tables.

Changes in IBProvider v3 [build 3.0.0.6327 RC3]

• We added ctype_user property that allows setting the encoding of data coming to client irrespective of the encoding in which this data is coming from database server.
• Support of Firebird and Interbase charsets aliases.
• We added ctype_none property that allows setting the charset for working with text data in NONE encoding.
• New algorithms of BLOB fields converting provide for quick work with flowing data, optimization of interaction with ICU library.
• Other important changes.

See detailed information on working with new character set processor in Firebird and Interbase charsets .

Text columns size in Firebird 2.x

IBProvider started to control text columns size when working with Firebird 2 servers in Unicode mode. If the length of loaded data exceeds the text column size the exclusion will be generated. To avoid column size checking connect in ordinary mode and set Unicode_mode=false.

Download IBProvider Professional Edition (64/32 bit)

• Support of 49 Firebird and Interbase code pages.
• Possible provider operation without registration in the system via manifest file.
• Prevention of memory leaks in Firebird client during library unloading.
• Specific errors have been fixed.

• IBProvider 1.9.11.2628
• IBProvider 2.6.5.2628
• IBProvider 3.0.0.5334 RC3

IBProvider v3 Release Candidate 3

Support of 49 Firebird and Interbase code pages

The new version of the driver supports all code pages of Firebird 2.1 , including UNICODE_FSS, UTF8 and OCTETS binary data.

Connection of external conversion algorithms

The new icu_library initialization property defines the path to DLL-library that serves ICU character sets. You can take ICU library from Firebird 2.1 set: icuuc30.dll. You shall also copy auxiliary DLL: icudt30.dll.

With icuuc30.dll connection you will obtain the opportunity of working with CP943C and GBK. character sets.

See the full list of Firebird and Interbase supported character sets .

IBProvider work without registering in the system

Access to Firebird and Interbase without installation of additional components in the operating system is topical for:

• WEB-applications on external hosting.
• Portable-applications connected to Firebird Embedded.
• Applications working with the database on the computer with limited user rights, without registering provider's COM-component.

The information about COM-component is included into client’s application manifest file. This eliminates the necessity to register IBProvider in the registry. This feature is supported by all the versions of IBProvider Professional.

Example of working with Firebird and Interbase without registering additional components .

Firebird client unload

Memory leaks were registered during fbclient.dll unload in the Firebird client’s library prior to Firebird 2.5 version. To prevent leaks dbclient_lock_rules feature has been added to IBProvider that defines the fbclient.dll unload rule.

Possible values of dbclient_lock_rules:
0 – unload the client after disconnecting.
1 – unload the client together with the provider. Default behavior.
2 – do not unload the client’s library at all.

Keeping dll in memory reduces fbclient.dll upload/unload overheads and makes the application work faster.

Download IBProvider Professional Edition (64/32 bit)

IBProvider builds:

• IBProvider 1.9.10.2557
• IBProvider 2.6.4.2557
• IBProvider 3.0.0.5068 RC3

IBProvider v3 Release Candidate 3

• Support of the following codepages added: DOS858, TIS620, BIG5, KSC_5601, GB_2312, SJIS_0208, EUCJ_0208;
• Bug in the errors handling for OUT-parameters of query was fixed;
• BLOB-fields access was improved;
• Memory management was improved;

IBProvider v2/v1

• BLOB-fields access was improved;
• Memory management was improved;

Download IBProvider Professional Edition (64/32 bit)

• Firebird Conference 2008 Timetable
• Register

Brief release annotation

IBProvider v3 Release Candidate 3 [build 3.0.0.4963]

• NUMERIC-types support was improved.
• Disabled metadata cache mode performance was increased in 2.5 times.
• Metadata schemes were updated. Among them in schemes TABLE_INFO and TABLES classification of external (EXTERNAL TABLE) and temporary tables (GLOBAL TEMPORARY PRESERVE/DELETE) was added starting from Firebird 2.1 and Interbase 7.5.
• Correct processing of active transactions in the connection pool.

New builds of IBProvider v1.9.9.2547 and IBProvider v2.6.3.2547

• BLOB-columns metadata description bug was fixed.
• Correct processing of active transactions in the connection pool.

IBProvider v3 Release Candidate 3 build 3.0.0.4963

NUMERIC-types support was improved

• Correct view of NUMERIC-columns types with zero scale. This feature will not work for and .
• Precisions for NUMERIC-columns were changed to 4,9,18. In previous releases precisions were equal to 5/10/19. Precision depends on base type in which NUMERIC is stored (SHORT, LONG or INT64).
• Changes are true for simple columns and columns with arrays.

Backward compatibility

3 initialization properties: n numeric_i2_rules, numeric_i4_rules, numeric_i8_rules for backward compatibility were added. Set these properties in getline on value 3 and you will rollback provider.

Common troubles with NUMERIC and solution

Common troubles with NUMERIC and solutions. Servers Interbase/Firebird/Yaffil implement simplified precision control. For example, they allow storing 32000 value in NUMERIC(4,0). MS SQL Server 2005 checks uploaded data precision. If data precision is not in the allowed range MS SQL will generate the error:

To define behavior of a provider in this case, use properties numeric_i2_rules, numeric_i4_rules, numeric_i8_rules.

Correct processing of active transactions in the connection pool

• When using SQL for transactions start ADODB may put connection with active transaction to the connection pool. As a result, when you open connection again pool may return connection with unfinished transaction. In IBP v1, v2, v3 initialization property reset_ds_tr_rule.
• Reset to initial state of session settings of the multiple connections was implemented.

Metadata query optimization for disabled metadata cache mode

If you disable metadata cache schema_cache=0 new build of IBProvider use query with parameters with limits considered.

This feature cuts traffic between client and server and increase running speed in 2.5 times with cache disabled if compared to previous versions. schema_cache=1 by default (metadata cache is enabled).

Classification of external and temporary tables

In TABLES, TABLES_INFO metadata schemes in TABLE_TYPE column new tables classifications were added:

• EXTERNAL TABLE - all server types and versions supported
• GLOBAL TEMPORARY PRESERVE - Interbase 7.5 , Firebird 2.1 or above.
• GLOBAL TEMPORARY DELETE - Interbase 7.5, Firebird 2.1 or above.

Other metadata changes

• In TABLES_INFO, TABLES schemes "EXTERNAL_FILE" column was added.
• In TABLES_OWNER scheme "TABLE_OWNER" column was added.
• Ignoring text case for column restriction in "TABLE_CONSTRAINT::CONSTRAINT_TYPE".

New builds of IBProvider v2, v1

• IBProvider v1 [1.9.9.2547]
• IBProvider v2 [2.6.3.2547]

Some features from IBProvider v3 RC3 are implemented

• Ignoring text case for field restriction in "TABLE_CONSTRAINT::CONSTRAINT_TYPE" was added.
• Correct interaction with connection pool.

Besides, a bug in BLOB-columns description was fixed

Due to the bug in release 2.6.1 (2.6.2), BLOB-columns were published with wrong flag DBCOLUMNFLAGS_ISFIXEDLENGTH.

Download IBProvider Professional Edition (64/32 bit) [build: 3.0.0.4963]