Automatic GO insertion after ; causes batch splitting issues

[WesleyDieterich]

Bug Description

When executing SQL scripts that contain semicolons (;) as statement terminators, DBCode appears to automatically inject a GO batch separator after each semicolon. This behavior breaks scripts that rely on variables, since variable declarations must remain within the same batch in SQL Server.

Repro steps

1. Open a SQL query editor connected to a SQL Server-compatible database (e.g., Fabric Warehouse)

2. Write a script using variable declaration and semicolons, for example:

   DECLARE @x INT;
   SET @x = 1;
   SELECT @x;
   

3. Execute the script using DBCode

4. Observe that the script fails due to unintended batch separation

Expected Behavior

The script should be executed as a single batch, respecting semicolons as statement terminators only, without injecting GO statements automatically.

Actual Behavior

DBCode appears to split the script into multiple batches by injecting GO after semicolons, causing errors in scripts that depend on variables or batch-scoped constructs.

Environment

• DBCode version: 1.35.8
• VS Code (or fork) version: 1.127.0
• OS: CachyOS and Windows 11
• Database: Fabric Warehouse
• Connection: Direct (SQL endpoint)

Error Meesages (if applicable)

Errors related to variable scope, such as:
"Must declare the scalar variable '@x'"

Screenshots

Logs

DECLARE @x INT;
GO
SET @x = 1;
GO
SELECT @x;
[137] Must declare the scalar variable "@x". (line 1)

[mikeburgh]

Thanks for all the info..

I just pushed 1.35.9 which should fix this.. It was working for SQL Server, but not fabric as I had different mapping there as I had aligned it with The SQL Server DW Azure also ships.

Can you confirm it works for you now, ? Also would you mind running these three statements on your Fabric warehouse and sharing the results, I don't have Fabric spun up at the moment, but think there is another tweak I can make.

 SELECT @@VERSION;

 SELECT SERVERPROPERTY('Edition')         AS edition,
         SERVERPROPERTY('EngineEdition')   AS engineEdition,
         SERVERPROPERTY('ProductVersion')  AS productVersion;

  -- does Fabric support OFFSET/FETCH?
 SELECT * FROM (VALUES (1),(2),(3)) v(n) ORDER BY n OFFSET 1 ROWS FETCH NEXT 1 ROWS ONLY; 

[WesleyDieterich]

I’ve just updated to the latest version, and it’s now working as expected. Thank you.

Regarding the queries you asked me to run, here are the results for each of them:

SELECT @@VERSION;

SELECT SERVERPROPERTY('Edition')         AS edition,
         SERVERPROPERTY('EngineEdition')   AS engineEdition,
         SERVERPROPERTY('ProductVersion')  AS productVersion;

SELECT * FROM (VALUES (1),(2),(3)) v(n) ORDER BY n OFFSET 1 ROWS FETCH NEXT 1 ROWS ONLY;