-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VARBINARY does NULL is not mapped correctly by default #232
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #232 +/- ##
==========================================
- Coverage 87.98% 87.71% -0.27%
==========================================
Files 8 9 +1
Lines 491 513 +22
Branches 68 74 +6
==========================================
+ Hits 432 450 +18
- Misses 48 50 +2
- Partials 11 13 +2 ☔ View full report in Codecov by Sentry. |
Thanks! Can you adjust the varbinary test here? SyncChanges/SyncChanges.Tests/Tests.cs Lines 199 to 245 in c7a7b7c
|
Later. I don't have any localdb sql server to test with. Could also add tests with transactions to see how they fail :-) |
Do you know why the current test succeeds? What would need to be modified for it to fail? |
It succeeds because varbinary(max) is not null. If you have a NULL value for it - it will fail. |
Thanks. I'll fix the varbinary test. Would be great if you could add transaction tests later. |
VARBINARY seems to be a special case which does not work correctly:
To work around this - check which columns can be nullable and are varbinary (maybe there are some more types?) - then insert SqlBinary.Null