Closed emreyigit closed 9 months ago
Name | Link |
---|---|
Latest commit | e6784f71e0f61c2f91f9e1b3a2854677853a4068 |
Latest deploy log | https://app.netlify.com/sites/silly-valkyrie-e996d9/deploys/65b258de6942930008077fad |
Attention: 1060 lines
in your changes are missing coverage. Please review.
Comparison is base (
7c75b2e
) 84.87% compared to head (e6784f7
) 80.76%. Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
If result of a SQL query contains
null
values, .Net client throws. See #854 for more details. This is because although SQL supports null for primitive types. The client cannot handle it. I've added nullable support for fixed sized type which are primitive ones.Also, current implementation were failing while parsing null or mixed result due to wrong assumptions on
List
. Defining a size during initialization, does not mean that the list created with null values. This is fixed in the PR.