- 08 5月, 2017 2 次提交
-
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
- 07 5月, 2017 18 次提交
-
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
It's indeed broken on their end. We should consider switching providers, e.g. https://github.com/mysql-net/MySqlConnector/
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
* Progress on VS 2017 build tooling * Finally, a working VS 2017 tooling build
-
- 05 5月, 2017 1 次提交
-
-
由 Per Lundberg 提交于
-
- 01 5月, 2017 1 次提交
-
-
由 Marc Gravell 提交于
-
- 30 4月, 2017 1 次提交
-
-
由 newbyca 提交于
-
- 07 4月, 2017 4 次提交
-
-
由 Marc Gravell 提交于
Add tests for the too few/too many columns scenarios for value-tuples; happy to discuss alternative expectations
-
由 Marc Gravell 提交于
Better matching of value-tuple names when wrong number of columns - should return nulls for unmapped
-
由 Marc Gravell 提交于
-
由 Marc Gravell 提交于
-
- 26 3月, 2017 2 次提交
-
-
由 Kruithne 提交于
Under the `List Support` section, the sentence opens with `Dapper allow you`, which should instead be `Dapper allows you`. This PR will correct this mistake, restoring balance to the universe. After originally spotting this, the most minor of mistakes, I decided to leave it and move on with my life, since it likely effected nobody. Four hours passed and the thought that it existed unchecked had fully manifested itself within my subconscious and I was no longer able to continue with my existence knowing that I had seen this mistake and not exercised my power to correct it. Thank you, and sorry.
-
由 Nick Craver 提交于
Due to the way VS test works (by injecting an executable entry point), the performance tests needed to be factored out. I also organized all of our existing tests better along the way. Actual code changes to Dapper itself are very minor, only formatting and documentation fixes (which we need many more of). The build.ps1 script is upated to work, but note that <frameworkAssemblies> is not working in .nuspec inside the packages in the new .csproj system. I consider this to be a blocker. Issue is here: https://github.com/NuGet/Home/issues/4853
-
- 14 3月, 2017 3 次提交
-
-
由 Jovan Popovic (MSFT) 提交于
* Added fix for Simple.Data tast Due to the missing .FirstOrDefault() in Simple.Data test, performance numbers for Simple.Data were too high (better than hand coded data reader). Added FirstOrDefault() to actually fetch the data.
-
由 Nick Craver 提交于
Update readme to remove notice about requiring open connections
-
由 Nick Craver 提交于
Added Belgrade SqlClient library in the performance benchmark
-
- 02 3月, 2017 2 次提交
-
-
由 Nick Craver 提交于
-
由 Nick Craver 提交于
-
- 01 3月, 2017 4 次提交
-
-
由 Marc Gravell 提交于
-
由 Marc Gravell 提交于
-
由 Marc Gravell 提交于
-
由 Marc Gravell 提交于
-
- 22 2月, 2017 1 次提交
-
-
由 Jovan Popovic 提交于
In the performance benchmark is added Belgrade Sql client data access library (https://github.com/JocaPC/CLR-Belgrade-SqlClient). This is a wrapper around ADO.NET classes that executes queries in async manner using callbacks. "Belgrade.Sql.Client": "0.6.2" is aded in project.json file, and new flag "BELGRADE" controls should the test be executed.
-
- 13 2月, 2017 1 次提交
-
-
由 Jovan Popovic 提交于
-