> Given all that, I propose to change the current behavior from "one > commit after each execute" to "one commit after FbCommand disposal" > when using implicit transactions. This could bring some breaks in > compatibility, but it will bring the performance near to levels similar to > the other providers.
If my opinion also counts: hmmmh... no, better not :-) Too much existing code would break, especially taking into account that a lot of "disposal" of FbCommand only takes place on shutting down the application (static commands?). And I don't think that expected behaviour should be changed with a high risk of breaking indeed a lot of existing code "only" to make reverse engineering into EF faster. If Jiri finds a way to implement an optional switch or property of the FbCommand class to set behaviour this or that way, but without breaking existing code, okay. I still would not touch it myself unless I am absolutely certain that I could 100% guarantee the end-of-life/disposal of a command object. The risk of creating stuck transactions is too high for me. best regards, André ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
