[release/7.x] Disable trigger enumeration on Azure Synapse Analytics, where triggers are not supported #31036
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ErikEJ
changed the title
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
timeout coincides with known issue with azure pipeline test cases. |
roji
changed the title
ajcvickers
approved these changes
Jun 8, 2023
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@roji Will this make 7.0.9 (assume July) ?? |
This will ship in August (7.0.10) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://learn.microsoft.com/azure/synapse-analytics/sql/overview-features
Fixes #30998
Description
Azure Synapse databases do not support triggers. We started checking for triggers in EF Core 7, which causes scaffolding from a Synapse database to fail.
Customer impact
Crash attempting to scaffold from a Synapse database. Workaround is to use the EF Core Power Tools, which have already been fixed.
How found
Customer reports 7.0
Regression
Yes.
Testing
Manual testing.
Risk
Low. Not quirked, because this is a design-time change.