We released new updates of our components for work with Firebird and InterBase:
- IBProvider v5.17
- LCPI ADO.NET Provider for OLE DB v1.20
- LCPI OLE DB Services v1.15
Also we created a new document – Integration Services. Using «LCPI ADO.NET Data Provider for OLE DB» as a data recipient.
Full news text – https://www.ibprovider.com/eng/news/n_200522.html
Kind Regards, IBProvider Team.
I’m now going through piece of SQL code that contains a lot of stored procedures from over the years and lately also functions (in last year the migration to Firebird 3 really began) and looking into the code to identify functions and procedures to start the rewriting with using FbNetExternalEngine. I’m at the beginning, but I have some interesting piece I’d like to show.
FbNetExternalEngine version 4.0 is finally here. This version contains one significant feature and that’s migration to .NET Core.
As you probably know, Firebird Conference 2019 will include the practical workshops, and the article “How to track deadlocks in Firebird” is one of the sneaks peeks of the workshop “All About Transactions”, which will be done by Vlad Khorsun, Firebird core developer, and Alexey Kovyazin from IBSurgeon.
To help developers investigate the update conflicts (deadlocks), Firebird puts into error messages the reference to the concurrent transaction – i.e., the transaction where the concurrent update is not yet committed. Together with Trace API, it gives us the ability to track both conflicting operations.
Let’s consider the practical steps on how to do it: read the article “How to track deadlocks in Firebird“.