-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Execution strategy for migration #17578
Comments
No, there are commands that cannot be executed in a transaction and therefore cannot be safely retried. |
But we could retry the ones that are in a transaction and do something fancy with Down operations or idempotent DDL statements (IF NOT EXISTS) to recover from failures outside of a transaction. |
I'm just looking for a built-in way to retry the connection itself, not any of the operations within it. |
When retrying without a transaction we can start from the last command that succeeded. |
Reopening to track reviewing my comments on #34206 (accidentally approved with auto-merge on). |
Dear all,
I am wondering if the SQL execution strategy specified when configuring the options for the context also covers the Migrate command when it takes place as part of the chain of events of the IWebHost as in the code sample in this discussion
The text was updated successfully, but these errors were encountered: