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 wrote the new small guide “Using «LCPI ADO.NET Data Provider for OLE DB» with Firebird SQL Server” and offer you acquainted with technological capabilities of our .NET provider.
From this article you can learn, for example:
- How to create multiple transactions within one connection
- How to work with parameters in queries
- How to execute SQL script
Your comments and suggestions are welcome!
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 >>>
Every year on January 18 we have a small celebration – IBProvider’s birthday.
This year it turned 14.
We thank all our users for using the provider in your projects.
We promise that we will continue to improve IBProvider till it completely supersedes Firebird and Interbase 🙂
Read more about the new features in Firebird and Interbase driver >>>
We are pleased to announce the new release of our OLEDB Provider: version 3.18.
Now in your projects for Firebird and Interbase you can more comfortable work with Linked Server of MSSQL 2012. Hurrah!
In new release:
- Improved performance of the provider as a linked MSSQL server.
- Provider compilation with Visual Studio 2012.
You can download IBProvider here: Firebird and Interbase driver >>>
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 >>>
We continue to develop our .NET Provider for OLEDB. In the new build (#1434), we have implemented the methods to obtain database metadata:
- All schemas of the OLEDB Provider
Distinctions compared to standard OLEDB.NET Provider:
- The SchemaGuids schema describes all schemas including SchemaGuids, DbInfoKeywords and DbInfoLiterals.
- The SchemaGuids schema supports restrictions for the Schema column.
Distinctions compared to standard OLEDB.NET Provider:
- The MetaDataCollections schema supports restrictions for the column CollectionName.
- The Restrictions schema supports restrictions for the columns CollectionName and RestrictionName.
- More accurate population of the DataSourceInformation schema.
- More accurate population of the Restrictions schema.
- Caching of data from its own schemas (SchemaGuids, DbInfoKeywords, DbInfoLiterals, …).
- Coherence of information from metadata schemas with the descriptions of the resulting rowset columns and command parameters (ensured by IBProvider).
- Different algorithms of metadata loading for Interbase and Firebird. Including – our provider takes into account the version of the server and the version of database ODS (ensured by IBProvider).
- Caching of OLEDB metadata schemas is carried out on the IBProvider level (see a property «schema_cache»).
- The OleDbSchemaGuid class added with the lists of known OLEDB schema identifiers.
- The OleDbSchemaRestriction class added with the lists of restriction indexes for known OLEDB schemas.
- The OleDbLiteral class added.
- The OleDbMetaDataCollectionNames class added.
- The number of tests and debug structures ensuring the correct work of components increased.
If you are interested in working with stored procedures grouped into PACKAGE, please take a look at the new example for our .NET Provider:
Creation and working with PACKAGE (C#, FB3)
A half year before we product first release of LCPI ADO.NET Data Provider for OLEDB, which became powerful alternative of standard .Net OLE DB Provider and provide advanced opportunities for all Firebird and Interbase users in .Net Framework:
- Automatic generation of command parameters which you do not need to enter manually anymore;
- Named and unnamed parameters, also IN, OUT and IN-OUT parameters;
- Connection pooling and SQL statement pooling which let your code run even faster;
- Nested («nested_trans=true») and distributed (TransactionScope, EnlistTransaction) transactions;
- All data types, including GUID, TIME (Dialect 3), DATE (Dialect 3) and multidimensional arrays;
- The MARS technology which enables working simultaneously with several active DataReader objects;
- And hey, ExecuteScalar now really loads one value only, not the entire record
- Multiple parameter-containing commands in one statement (SQL scripts);
Up to this day LCPI ADO.NET Data Provider for OLEDB was available only in professional version of IBProvider but now you can download it on the download page together with first release of IBProvider in the new year:
You cand download Firebird OLE DB Provider and ADO .Net Data Provider here.
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
We are continuing to actively add new functionality of Firebird 3 DBMS to IBProvider.
Let us remind you that already 2 months ago we added support of BOOLEAN data type from Firebird 3. In the new version of IBProvider Professional, we added support of PACKAGE instruction.
Now you can put in order a bulk of database procedures and functions and group them by sense into individual modules (PACKAGE). This arrangement will substantially simplify understanding and maintenance of SQL code.
Ream more about Firebird 3 access improvements.