Conversation
Adds a Migrations section covering the dual Dapper/EF tracks, paths to the SSDT project and DbScripts, links to the contributing-docs MSSQL migration and SQL code style guides, and the local commands for applying migrations and regenerating EF migrations across all three providers.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7689 +/- ##
==========================================
+ Coverage 60.20% 60.40% +0.19%
==========================================
Files 2137 2136 -1
Lines 94412 94548 +136
Branches 8409 8434 +25
==========================================
+ Hits 56840 57108 +268
+ Misses 35580 35437 -143
- Partials 1992 2003 +11 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| - OpenTelemetry for observability (ADR 0020) | ||
| - Log to standard output (ADR 0021) | ||
|
|
||
| ## Migrations |
There was a problem hiding this comment.
❓Is this information Claude always needs, or only when dealing with schema changes? If the latter, can we convert this to a new Skill, or fold it into writing-database-queries?
There was a problem hiding this comment.
Only with db schemes. Not sure if the skill was triggered or not but if it was it is in-sufficient. I observed. the following defects.
- Hand wrote MySQL migration because the docker wasn't running. This should be forbidden.
- Used the wrong T-SQL syntax.
There was a problem hiding this comment.
Gotcha. Can we verify if it was invoked, and if the instructions need to be updated? If it wasn't invoked when you expected we should be able to adjust the skill's description or when_to_use fields to improve hits from natural language and inference.
There was a problem hiding this comment.
How do I do that? If you want to take ownership of bringing in this change that's fine too, I just don't want this happening again.
2 participants
🎟️ Tracking
📔 Objective
Adds a Migrations section covering the dual Dapper/EF tracks, paths to the SSDT project and DbScripts, links to the contributing-docs MSSQL migration and SQL code style guides, and the local commands for applying migrations and regenerating EF migrations across all three providers.