How to use "use" binding in SqlTransaction - f#

Question

In MSSQL Server I have a database named TestDB that contains a single table with three column (Id, FirstName, LastName) named TestTable. To insert rows into TestTable I have declared a type
type Person = { Id:int; FirstName:string; LastName:string }
two methods 1) Parameters and 2) Transaction
let Parameters(person:Person) =
[|
SqlParameter("#Id", person.Id)
SqlParameter("#FirstName", person.FirstName)
SqlParameter("#LastName", person.LastName)
|]
let Transaction(tsql, sqlcon, sqltran, sqlparam) =
let cmd = new SqlCommand(tsql, sqlcon, sqltran);
for p in sqlparam do
cmd.Parameters.Add(p) |> ignore
cmd
in main method of my Console Application I have used the type and methods in this way
let population = [{Person.Id = 1; Person.FirstName = "Emon1"; Person.LastName = "Haque1"}
{Person.Id = 2; Person.FirstName = "Emon2"; Person.LastName = "Haque2"}]
let query = #"INSERT INTO TestTable VALUES(#Id, #FirstName, #LastName)"
let conStr = #"server=EMON; database=TestDB; user=TestUser; password=TestPass"
use con = new SqlConnection(conStr)
con.Open()
let trans = con.BeginTransaction()
try
population
|> List.iter(fun x -> Transaction(query, con, trans, Parameters(x)).ExecuteNonQuery() |> ignore)
|> trans.Commit
with
| exn -> trans.Rollback()
I have used use once for SqlConnection in main method.
Should I use it for SqlCommand in Transaction function, con.BeginTransaction() and in case of calling Transaction as it returns SqlCommand in main method or use con will take care of all?

Answer 1

If you're familiar with C#, then use works like using in C#. When the values go out of scope, Dispose is called. As a general rule, if you don't use values, then Dispose isn't called.
Some .NET APIs have options for disposing of contained disposable. As an example, StreamReader will automatically dispose of the Stream is contains, unless explicitly constructed with a constructor overload where you can override that behaviour.
As far as I'm aware, though, there's no consistency in such APIs, so you can't rely on hierarchies of disposables to behave that way.
Specifically, I don't see any overloads of BeginTransaction that specify how the returned transaction relates to the connection that created it, and the documentation doesn't say, either. I'd use the trans value, instead of hoping that ill-defined behaviour in the BCL will do the right thing.