WIP: Analysis: Cannot remove legacy database system without EF Core replacement #70
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
joezombie/castr!70
Loading…
Reference in a new issue
No description provided.
Delete branch "copilot/remove-legacy-database-system"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This issue requests removal of both
PodcastDatabaseService(per-feed databases) andCentralDatabaseService(centralized database) as part of Epic #58 "Migrate to Entity Framework Core". However, no EF Core implementation exists in the codebase.Blocking Issues
No replacement system available:
Castr.csprojDbContext, repository interfaces, or EF Core migrationsAddCastrDatabase()extension method referenced in issueActive dependencies prevent removal:
CentralDatabaseServiceused by:Program.csfor feed migration and episode syncingPodcastDatabaseServiceused by:PodcastFeedServicefor RSS feed generationPlaylistWatcherServicefor YouTube download trackingPossible Interpretations
PodcastDatabaseService, retainCentralDatabaseServiceas the "new" systemRecommendation
Clarify intent before proceeding. Removing both services without a replacement will break:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Closing as this is an analysis document, not implementable code. The analysis correctly identifies that the legacy database system cannot be removed until EF Core migration (Epic #58) is complete. This dependency is tracked in the epic.
Pull request closed