-
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
Script-Migration -idempotent creates script with errors #19740
Labels
Comments
Not exactly a dupe. CREATE PROCEDURE calls are tricky since they need to be the first statement in a batch. EF6 wraps them inside EXEC:
|
This was referenced Jan 30, 2020
Closed
Linked to docs: dotnet/EntityFramework.Docs#694 |
@sdpollack In case I was too subtle, you can work around this by changing your migration to use EXEC: migrationBuilder.Sql(@"
EXECUTE('
CREATE PROCEDURE ...
')
"); |
16 tasks
Tracked by documentation and #245 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I'm trying to create an idempotent migration script (as I've done previously). The resulting script won't load due to errors.
Steps to reproduce
Loading the script in VS shows 3 errors. Running the script results in 5 errors.
sd5bgmh0.txt
Msg 156, Level 15, State 1, Line 792
Incorrect syntax near the keyword 'procedure'.
Msg 156, Level 15, State 1, Line 1255
Incorrect syntax near the keyword 'procedure'.
Msg 137, Level 15, State 2, Line 1268
Must declare the scalar variable "@unitid".
Msg 156, Level 15, State 1, Line 1306
Incorrect syntax near the keyword 'procedure'.
Msg 137, Level 15, State 2, Line 1324
Must declare the scalar variable "@parentUnitId".
Msg 102, Level 15, State 1, Line 1333
Incorrect syntax near ')'.
Further technical details
EF Core version: 3.1.1
Database provider: Microsoft.EntityFrameworkCore.SqlServer 3.1.1
Target framework: .NET Core 3.1
Operating system: Windows 10 Enterprise 1909
IDE: (e.g. Visual Studio 2019 16.3) VS 16.4.2
The text was updated successfully, but these errors were encountered: