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.

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

Jump to bottom

Revisit usage of stored procs vs EF & LINQ #310

Open
aaronpowell opened this issue Jul 5, 2024 · 0 comments
Open

Revisit usage of stored procs vs EF & LINQ #310

aaronpowell opened this issue Jul 5, 2024 · 0 comments
Labels
api Python backend service
Milestone
Proxy .NET migration

Comments

@aaronpowell
Copy link
Contributor

With #306 making the proxy also .NET, we should revisit where we're using stored procs and whether we can achieve the same with LINQ to ensure more type safety in the database access and potentially move to using EF Code First + Migrations for DB schema management.
@aaronpowell aaronpowell mentioned this issue Jul 5, 2024
Merged
@aaronpowell aaronpowell added this to the Proxy .NET migration milestone Jul 6, 2024
@aaronpowell aaronpowell added the api Python backend service label Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api Python backend service
Projects
None yet
Milestone
Proxy .NET migration
Development

No branches or pull requests
1 participant
@aaronpowell