Closed plushy closed 11 years ago
The issue regarding multiple queries in a series without a separator isn't really a bug I can fix; that's essentially user-error (if the user is expecting to seem them all).
The GO issue is a bug I will look at, however. Thanks
Yeah, I wasn't sure about those semicolons (the query plan doesn't connect those other queries with a line). But it seems sql server handles it somehow: http://i.imgur.com/xOVANsI.png http://i.imgur.com/WQFDFDv.png I don't use MSSQL personaly so I don't really understand that semicolon optional thing and dunno if people expect it. I'll trust your opinion on that.
I could be wrong on this, but I believe the limitation is actually at the JDBC level.
Resolved with 6a7ab6c229729c450dd398c3c4411797961f8ef8
Only one result from a series of queries not terminated with a semicolon is displayed (thanks to Twist-, cairnz for helping to find the bug): http://sqlfiddle.com/#!6/189a3/1058 Also GO as the last line breaks the result: http://sqlfiddle.com/#!6/189a3/1069 It doesn't happen if there is a space or enter after GO.