Disabling database triggers in FirebirdClient (.Net)

Via Jiří {x2} Činčura blog:

Database triggers are a nice new feature added to Firebird in version 2.1. And as you can do a lot of stuff with them, sometimes you also might wanna to connect without firing these, especially if you made a mistake there and it’s forcibly closing your connection. :) To disable these, standard Firebird utilities have a new switches. But it boils down to the API itself, nothing magical.

And if it’s in API, it could be FirebirdClient, right? In last few days among working on other bugs and my daily responsibilities I had a time to dig into this. And now also from .NET world we can use this feature.

Firebird 2.0.x branch with four months changes in review

Alex Peshkoff backported fix for CORE-3736: WITH LOCK clause is allowed for users with read-only rights on some table, thus blocking others from updating this table.
Dimitr backported CORE-3730: isc_dsql_exec_immed2() loses input parameter value with RETURNING clause.
And then he updated the docs for 2.0.7 release
Horsun Vlad backported fix for bug CORE-2977 that was in Firebird 2.1.x incorrectly works with indexed fields of type DATE in OLD ODS (9.1).
Paul Beach made modifications in 2.0.7 so it can be compiled and build on OSX.
Paul Reeves synced 2.0.7 branch with B2_0_Release.
In the end Paul Beach made in the conf. parameter DummyPacketInterval more accurate.

1 109 110 111 112 113 297