Skip to content

Document difference in DateTime vs TimeSpan value for DbType.Time parameter #1173

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.

Sign up for GitHub

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

Merged
cheenamalhotra merged 2 commits into from
Jul 23, 2021
Merged

Document difference in DateTime vs TimeSpan value for DbType.Time parameter #1173

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
25d1e7c
Update porting-cheat-sheet.md
natehitze Jul 14, 2021
6c9adc4
Update porting-cheat-sheet.md
natehitze Jul 15, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions porting-cheat-sheet.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,13 @@ For .NET Framework projects it may be necessary to include the following in your
</configuration>
```

## Functionality Changes

| System.Data.SqlClient | Microsoft.Data.SqlClient |
|--|--|
| Can use DateTime object as value for SqlParameter with type `DbType.Time`. | Must use TimeSpan object as value for SqlParameter with type `DbType.Time`. |
Comment thread
cheenamalhotra marked this conversation as resolved.
| Using DateTime object as value for SqlParameter with type `DbType.Date` would send date and time to SQL Server. | DateTime object's time components will be truncated when sent to SQL Server using `DbType.Date`. |

## Contribute to this Cheat Sheet

We would love the SqlClient community to help enhance this cheat sheet by contributing experiences and challenges faced when porting their applications.