Skip to content

fix: EF Core logs from Warning up, not every SQL command - #44

Merged
ThorSPB merged 1 commit into
mainfrom
fix/43-ef-command-logs
Oct 14, 2026
Merged

ThorSPB merged 1 commit into
mainfrom
fix/43-ef-command-logs

Conversation

@ThorSPB

@ThorSPB ThorSPB commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Closes #43

What

  • appsettings.json: Microsoft.EntityFrameworkCore at Warning. This applies to the API and to the timetable import, which reads the same file; the import's own Warning minimum was being overridden by Default: Information.
  • README: the config row says how to see SQL again while debugging.
  • Test: SQL commands are off at Information, EF warnings stay on, the app's own Information stays on.

Testing

  • CI. Without the setting, Default: Information applies and the first assertion fails.
  • After deploy: stage's api.log gets no new Executed DbCommand entries, and an import dry run prints only the summary and warnings.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ThorSPB
ThorSPB merged commit 053d1da into main Oct 14, 2026
3 checks passed
@ThorSPB
ThorSPB deleted the fix/43-ef-command-logs branch October 14, 2026 11:02
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.

EF Core logs every SQL command at Information (API log and the import output)

1 participant