SQL Server migration batch terminator as first statement gives empty query error

[mpapetti]

What version of Flyway are you using?

4.2.0

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)

CLI

What database are you using (type & version)?

SQL Server 2016

What operating system are you using?

Amazon linux

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)

Tried to run a migration with the following as the first few lines:

/*
 some comment
*/
GO
SET NOCOUNT ON
SET NOEXEC OFF
SET ARITHABORT ON

I ran flyway -url='mydburl/mydb' -locations='mylocation' migrate

What did you expect to see?

I expected the migration to run successfully

What did you see instead?

The migration ran fine when I removed GO. When I put GO as the first line of a migration, it will fail with the error below. Is it possible for flyway to ignore this line if no query exists before it? I suggest a simple regex to identify:

• If a migration's GO or batch terminator (or configured terminator) has an actual query preceding it or just some comments
• Based on previous, ignore the batch terminator if comments are found or run the query if it is found

SQL State  : HY000
Error Code : 0
Message    : The SQL statement must not be null or empty.
Location   : myMigration.sql 
Line       : 4
Statement  : 

Thanks!

[axelfontaine]

This is now working. (Make sure to use the newly bundled MS driver)

[mpapetti]

You da man, thank you!!

…

On Mon, Dec 18, 2017 at 8:50 AM Axel Fontaine ***@***.***> wrote: Closed #1838 <#1838>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1838 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ac3HbOGFQt3P0pvg6UTLow4PPrvdtdsvks5tBm2QgaJpZM4QoroI> .