Thanks for getting back to me.
Can you or anyone please let me know what is the recommended approach in
the ADO.NET provider for performing a transaction across, let's say, 2
databases (eg a single command in each)?
On 5 November 2016 at 08:37, Jiří Činčura <j...@cincura.net> wrote:
> I don't think the TransactionScope block is a good idea here (well, it
> never is). Having it between multiple databases mean spinning MSDTC and
> enlisting there. I don't remember from top of my head whether that works
> in FirebirdClient or not. And the ChangeDatabase is ADO.NET non-sense
> for MS SQL. In Firebird you can't switch databases. You just need to
> open another connection (which is what the implementation does). So I
> suppose some transaction is still dangling there on 2nd run.
>
> --
> Mgr. Jiří Činčura
> Independent IT Specialist
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Firebird-net-provider mailing list
> Firebird-net-provider@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
