Skip to content
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

Fixed issue #541 in README.md #577

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

ckadluba
Copy link
Member

The Timestamp column is nullable by default but the README.md stated the opposite. This was fixed now.

The Timestamp column is nullable by default but the README.md stated the opposite. This was fixed now.
@ckadluba ckadluba linked an issue Sep 26, 2024 that may be closed by this pull request
@ckadluba ckadluba added this pull request to the merge queue Sep 26, 2024
Merged via the queue into serilog-mssql:dev with commit 614dbc9 Sep 26, 2024
4 checks passed
@ckadluba ckadluba deleted the 541-timestamp-default-nullable branch September 26, 2024 15:35
@cremor
Copy link

cremor commented Oct 3, 2024

Thanks, but why is the column actually nullable? How can there be a log line without a timestamp?

@ckadluba
Copy link
Member Author

ckadluba commented Oct 4, 2024

That's a good question. It can probably be answered only by the initial developers of this sink (which was not me :)). Now it is like it is and changing it would maybe break existing applications using the MSSQL sink. I agree with you, that a log entry without a timestamp is not quite useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TimeStamp column nullable or not
2 participants