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

Recognise first run better when calling UpdateSchema #1

Open
jakeahumphreys opened this issue Jan 8, 2025 · 0 comments
Open

Recognise first run better when calling UpdateSchema #1

jakeahumphreys opened this issue Jan 8, 2025 · 0 comments
Labels
smelly I should look at finding a better way of doing this

Comments

@jakeahumphreys
Copy link
Owner

Currently I've been lazy and just caught the exception thrown when we're in the situation where we've created the database file, but need to run a schema update to fill out the missing tables. It runs a query to get schema versions, but it can't run the query because the table doesn't exist. So right now I catch that exception, set CurrentVersion to null and do the update.

Ew.

@jakeahumphreys jakeahumphreys added the smelly I should look at finding a better way of doing this label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
smelly I should look at finding a better way of doing this
Projects
None yet
Development

No branches or pull requests

1 participant