optional parameter for CLIMutable record result

[fsprojects]

optional parameter for CLIMutable record result

[dmitry-a-morozov]

@jackfoxy Do you need one-way (from record to json) serialization or two-way (from json to record too) ?

[jackfoxy]

Record to JSON would really be a nice feature for SqlCmd.

I will be receiving posts with JSON that is almost like table row in my database, but I am assuming I will parse with Newtonsoft JSON (or similar) to build in code SQL for SqlCmd. This will be the first time I have updated/inserted w/ SqlCmd. Does it support UPDATE/INSERT from record instead of explicit SQL? The JSON I will receive does not correspond to all the SQL columns I need for an INSERT (and also not for an UPDATE), and there is probably going to be a little logic involved, so if you did implement something like JSON to SqlCmd record I might not be able to use it anyway.

[jackfoxy]

One more thing... Record to JSON from SqlCmd in some other way than CLIMutable solves one hassle and creates another, as now I need to tell the "automagic" in WebAPI to emit JSON I have explicitly built. (I'm sure it's easy to do, just one more thing for me to learn and one more workaround to put in the code). At this point I don't know enough to evaluate the trade-off.

[dmitry-a-morozov]

I meant to write for docs to show update examples but here is sample code
https://github.com/fsprojects/FSharp.Data.Experimental.SqlCommandProvider/blob/master/src/SqlCommandProvider.Samples/WpfDataBinding/Program.fs#L29
Basic idea is to create SqlDataAdapter based on original command.
So you might want to use ResultType.DataTable.
I believe Json.NET can be configured to support DataTable via DataTableConverter.
http://james.newtonking.com/json/help/index.html?topic=html/T_Newtonsoft_Json_Converters_DataTableConverter.htm
In general speaking of Records serialization, I think I might change SqlCommnadProvider to erase ResultType.Records to dynamic objects instead of obj[]. This should help.

[dmitry-a-morozov]

Release 1.1.25