597cc69ba5
2.0 RTM
2019-08-29 14:17:14 +01:00
522bc49a99
rev Microsoft.Data.SqlClient to GA (1.0.19239.1)
2019-08-28 17:09:18 +01:00
f5ca275a29
release notes
2019-08-28 15:26:35 +01:00
8152f2c718
WIP: Lib updates and prepare for Microsoft.Data.SqlClient ( #1313 )
...
v2 work; primarily prep for split SqlClient
2019-08-28 15:07:32 +01:00
6df95cbdbd
Expose the underlying connection from Rainbow Database so it's easier to use Dapper alongside other DB frameworks ( #1257 )
2019-08-27 17:33:14 +01:00
012e9b6f08
Add ability to override Dispose() in the derived class ( #1256 )
2019-08-27 17:32:51 +01:00
4eeb632fd5
Fixed issue #569 with IN and other condition. ( #1146 )
2019-08-27 17:03:49 +01:00
f1ad61c711
Use LocalBuilders rather than hardcoding or passing local indexes ( #1282 )
...
* Pass LocalBuilders instead of indexes since ILGenerator already optimizes the opcode used
* Eradicate magic local indexes to make refactoring safer
2019-08-27 17:01:34 +01:00
6754fe2795
Add ExecuteReaderAsync overloads that return Task<DbDataReader> ( #1295 )
2019-08-27 16:52:43 +01:00
8b49eb691d
Stop setting current index local which is nonexistent in ValueTuple deserializer ( #1280 )
...
* String and byte[] tuple elements cause InvalidProgramException
* Stop setting current index local which is nonexistent in ValueTuple deserializer
2019-06-13 07:37:41 +01:00
fcd8a70279
reinstate SqlDataRecord types (major conflict with MSSQLCLIENT, but that is removed for now)
2019-06-12 19:39:12 +01:00
67e3b33896
remove ui test from sln
2019-06-12 16:27:27 +01:00
28de4690d8
UI binding test: making build painful - kill it
2019-06-12 16:26:27 +01:00
9fbba78da0
Make Dapper happy with Microsoft.Data.SqlClient ( #1262 )
...
* prep work for adding Microsoft.Data.SqlClient support/tests; SqlClient dependency is not yet removed
2019-06-12 16:24:38 +01:00
33d974a5c0
Fixes mapping for C# tuples with more than seven elements ( #1242 )
...
* Failing tests for tuples larger than 7
* Special-case IL generation for ValueTuple
* Make value-processing logic available to ValueTuple generation
2019-06-12 16:16:45 +01:00
a5256b7d94
Remove .NET 45 in XML docs ( #1271 )
2019-06-03 14:05:12 +01:00
d19d6012e7
fix #1228 - rev sqlclient to 4.6.0 ( #1229 )
...
* fix #1228 - rev sqlclient to 4.6.0
* use transitive deps for SqlClient
2019-04-05 11:39:04 +01:00
c1d0fd870d
typo on release note version
2019-03-30 17:30:33 +00:00
23ff459f9d
release notes
2019-03-30 17:22:50 +00:00
d669d141f3
descriptor API: use index rather than constantly looking up the name
2019-03-30 17:20:28 +00:00
733d1734ca
When reading Geometry and Geography values from the database, we need to specify the SRID explicitly to retain it in the DbGeometry / DbGeography type. ( #1038 )
...
merging, thanks, and sorry for delay
2019-03-27 09:18:05 +00:00
3bf2b4f703
support the descriptor (component-model) API ( #1216 )
2019-03-27 09:12:06 +00:00
f0da900ee6
Fix Typo ( #1215 )
...
thanks, appreciated
2019-03-26 02:16:20 -07:00
684d7d9895
Add release notes for 1.60.1
2019-03-03 08:57:20 -05:00
b520e26a25
Bump version to 1.60.0 ( #1198 )
...
This bumps and locks at 1.60.0 to cope with whatever binding policies .NET Core is enforcing - then we can stick at this until 2.x I guess.
2019-02-25 10:05:21 -05:00
200f031ce4
Release notes issue links ( #1195 )
...
This PR is for the issue I raised earlier #1194
- I've added links for all every issue
- Tidied up capitalization
Let me know if you need me to make any changes
2019-02-20 09:29:18 -05:00
e7020b2bde
release notes for 1.50.7; set future versions to 1.50.8-alpha
2019-02-11 12:26:07 +00:00
bed688bbe8
version for public drop
2019-02-11 08:44:46 +00:00
68eea4ff26
fix #1190
2019-02-09 12:22:11 +00:00
b961089eff
Improve Exception message ( #1154 )
...
In cases where the object has a property named ID, the property will automatically be assigned as [Key], even if [Computed] is added manually in an attempt to override it. This can cause confusion, this exception will be thrown despite the code looking fine and there only being one [ExplicitKey] defined. I've added this extra line of information to help diagnosis.
2019-02-09 07:19:33 -05:00
5927c66776
Mention how to use user defined variables ( #1149 )
...
Fixes #620
Added a section to indicate Dapper works well with User Defined Variables.
2019-01-27 08:50:08 -05:00
b4c6d5eff4
Fix typo ( #1155 )
2019-01-27 08:45:27 -05:00
82a0059535
Add the eXpress Persistent Objects (XPO) benchmark ( #1131 )
2018-11-01 20:58:49 -04:00
ec194429cd
Corrected class name from PostcresqlTests to PostgresqlTests ( #1144 )
2018-11-01 20:56:06 -04:00
48f6754ad6
Updte literal example to be a bit better
2018-09-11 22:28:11 -04:00
d702fb82eb
Update benchmarks to latest run
2018-09-11 21:54:40 -04:00
c5f884de9b
Fix benchmark stability
...
Lots of runs is good, but changed behavior and greatly affects stability (due to GC).
2018-09-11 21:49:42 -04:00
2a2ff86561
Fix Dapper.Contrib to prefer its attribute but still fall back to others
2018-09-11 20:59:15 -04:00
0ec089b7d2
Benchmarks: normalize names and give ORMs better names via [Description]
2018-09-11 18:04:35 -04:00
b262cb33dd
Added Dashing Benchmarks ( #1126 )
...
Adds Dashing benchmarks to Dapper.Tests.Performance
2018-09-11 17:44:34 -04:00
5256f2ea0b
Benchmarks: Linq2DB tidy
2018-09-11 17:41:58 -04:00
9313e9f1f8
Added Linq2DB benchmarks ( #1125 )
...
Added Linq2DB benchmarks
2018-09-11 17:39:12 -04:00
0b867bbfa2
Add EF compiled query to benchmarks
2018-09-10 20:37:19 -04:00
0b168789fd
Benchmarks: updating libs and overall runner ( #1123 )
...
This is prepping a run we can drop into the README easily. And more info on allocations and such along with it. It's finishing off the benchmark port getting it into a good output state (something we can copy/paste). It removes Simple.Data because the package was debug and causes a lot of issues.
This doesn't output 100% like we want yet (fastest to slowest). BenchmarkDotNet joins summary results after ordering...we need to post-order that. I'm asking the maintainers how to do so.
Also note Belgrade was not parameterizing before, giving it a huge unfair advantage. This has been fixed to be apples:apples.
2018-09-10 20:22:10 -04:00
6e2774064d
Make SqlMapper.Parse consistent with QueryImpl, closes #1111
2018-09-06 20:33:27 -04:00
5189fcd43a
Tests for #1111 - Inconsistent deserialisation between normal Query<T> and SqlMapper.Parse<T>
2018-09-06 20:33:27 -04:00
522d150e25
Faster builds + use MySqlConnector
...
MySql.Data is a travesty at this point - moving to something more stable. Really we weren't testing Dapper with previous test failures, we were testing what mood MySql.Data and NuGet extraction are in and which phase of the moon is about.
Also speeds up the builds with 1 restore and 1 build. We can simplify here because everything is relevant (no wasted builds).
2018-09-03 21:38:27 -04:00
ba16b54b4f
Woops, fix appveyor config for new build.ps1
2018-09-03 20:36:51 -04:00
e16c69950c
Dapper build fixes, versioning, and SQL CE drop
...
- Moves to NerdBank git-based versioning
- Cleans up build.ps1 to current (will tweak for older moves later)
- Updates xUnit to latest
- Moves to dotnet test, since they killed dotnet xunit
- Testing SQL Server CE has become unreasonable. It's gone (minimal cleanup in this commit disabling it).
2018-09-03 20:35:06 -04:00
1cd3efd894
More detailed error message on unsupported literal type ( #1100 )
...
instead of exception message of `DateTime`, you'll get `The type 'DateTime' is not supported for SQL literals.`, which is much more helpful when trying to figure out what went wrong
2018-08-22 09:00:02 -04:00
mgravell