Migrations: creating memory optimized table throws warning as error when applying migration because it can't be executed in a transaction #34829
Labels
area-migrations
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
model:
error
problem here is that this is a single operation from a user's perspective (it's only multiple operations under the hood). Only option seems to be suppressing the warning, but this user experience is not great.
here is the sql that's being generated
The text was updated successfully, but these errors were encountered: