For fans only:
For the first time, we managed to perform all IBProvider system tests applicable to Firebird v3 in one run. This took 26 days and a ten-core processor.
Full note text: https://www.ibprovider.com/eng/news/n_181010.html
We have released an update of IBProvider, which has the solution for error with code 8152 of MS SQL Linked Server.
Short annotation of this problem – MS SQL has the problem with processing of object descriptions in metadata schemas.
New provider allows you do not publish object descriptions in schemas.
You may turn off publication of object descriptions to speed up the process of loading metadata schemas as a whole.
We present new personal license for 32-bit IBProvider called «One Time Personal License (32-bit)».
The new license is meant for all those who would like to create small programs for Firebird and InterBase for WIN32 and .NET platforms.
This is the same full-featured 32-bit provider (prof and lite editions) that is included into licenses for developers and MS SQL. It does not have any technical or time restrictions.
The price for new license is quite symbolic: 99+1 EUR.
Read full news text: http://www.ibprovider.com/eng/news/n_180521-one_time_personal_license.html
We are glad to announce the new update of IBProvider — v3.50.
Main feature of this release — elimination of very old restrictions of our OLE DB provider.
Common list of changes:
- Better support of MS SQL
- Support of data rereading for updatable sets
- Improved error handling
- Specific data processing errors fixed
- Support of FB 3.0.4 added
We have two news for you:
1. IBProvider v3.49 was released. We ensured a stricter compliance with the OLE DB specification and revised the existing code.
2. Microsoft changed its decision to go back to ODBC and promises to release an updated OLE DB provider for MS SQL. Let’s hope that they not only will rewrite the provider but also update the OLE DB specification.
New release v3.43 of our “Native OLE DB provider for Firebird and InterBase” available for download.
- The support of primary version of ICU from Firebird v3 (ICU v5.2) has been added
- Loaders of metadata schemas have been improved
We are pleased to announce the new update of IBProvider – v3.40. There are not a lot of changes in this release. However, it was very well tested. Including with a our new connection pool, which we will present in a month.
Full news text: http://www.ibprovider.com/eng/news/n_170415.html
We are pleased to announce the release of our “LCPI ADO.NET provider for OLE DB” which allows to create a professional solutions for Firebird!
Our .NET provider doesn’t force you to use ADO.NET as the exclusive access technology in application. You can use ADODB and work with OLEDB provider directly. Simultaneously!
You can use any .NET programming language and any programming language that supports COM or ActiveX. All at once!
And, of course, you can be sure in quality of this ADO.NET provider. We used TDD from beginning to end of development cycle.
Read the full text of press release here – http://www.ibprovider.com/eng/news/n_150408_adonet_provider_release.html
We are pleased to announce the release candidate of our .NET Provider for OleDb.
Now you can use 200% of the ADO.Net power in your projects for Firebird and Interbase:
- Read sets via OleDbDataReader and change them simultaneously (MARS technology).
- Use nested transactions, savepoints and distributed transactions within the TransactionScope.
- Execute several select, update and insert queries with parameters(!) within only one command OleDbCommand.
- Work with absolutely all types of data, including arrays and even Interbase Guid.
- And yes, now after you have set the command text you don’t need to manually add parameters to the query. Everything is done automatically and on the fly.
You can download ibprovider here: Firebird OleDb driver >>>
If you have ever worked with Firebird or Interbase using the standard .NET provider for OLE DB (System.Data.OleDb), you will have likely encountered issues like this:
- The necessity to add ALL parameters manually.
- Even though the OLE DB provider supports parameter generation for commands, the .NET provider doesn’t use it, so you as the programmer must do that work on your own.
- The lack of support for named parameters. Although they actually exist, using them in reality requires a whole set of complex manipulations (the steps needed to add a parameter to a collection, etc.).
- The impossibility of using multiple DataReader objects at the same time (Multiple Active Result Sets).
- No execution of SQL scripts which contain several SQL expressions per command. This list of difficulties a .NET developer has to deal with is far from complete. Now it’s all different in a fundamentally new .NET Data Provider for OLE DB