Tuomas Hietanen

I think this is increasing problem when SQLProvider is getting better to handle more complex queries when your business logics starts to locate more and more in the SQL query,...

Also I think this would be an advantage over e.g. FSharp.Data.SqlClient and many others, in an enterprise environment, you could actually unit-test your database query logics.

I went for having a test-database. That wasn't what I wanted back in 2017 when I asked this, but it was enough. I can just play with any code by...

fieldNotation is how it serializes the field. It has a parameter SqlColumnType where is a column type, at some level. The problem is of course that if you use a...

True, fieldNotation has only the .NET type (String in this case)

Silly question, what if you do: ```fsharp query { for x in xs where x.MyJSonColumn.ToString() = "test" } ``` That will do the comparison as text, not in Json. Will...

What could be done is: - Custom method e.g. ParseJSon(x) for strings. The method can be a function in SQLProvider namespace like the current e.g. `let ParseJson (a:'a) = ""`....

Just a quick look into this one, it seems that something in `this.ReadEntities` goes wrong: - The SQL-query is correct as far as I know, `SELECT [p].[MYCOLUMN_ID] as '[p].[MYCOLUMN_ID]' ...`,...

Seems like you mix mscorlib.dll (.net framework) and netstandard.dll somehow

Related to #400 and #399