Fix SET TERM handling in SQL execution

[Copilot]

SQL scripts containing SET TERM were failing with "Token unknown" errors. The code was splitting statements on ; delimiters, which breaks when SET TERM changes the terminator to ^ or other characters for trigger/procedure definitions.

Changes

Detection and routing

• Detect SET TERM pattern (/\bSET\s+TERM\s+/i) before splitting
• Route entire script to isql CLI tool instead of fbird_query() when detected
• Skip semicolon-based splitting to preserve custom terminators

Example failure case:

SET TERM ^ ;
CREATE OR ALTER TRIGGER XXX_YYY0 FOR AAAAAAAA
ACTIVE BEFORE DELETE POSITION 0
AS
BEGIN
  -- trigger body
END;^
SET TERM ; ^

Previously: Split on ; → invalid fragments → SQL error
Now: Pass complete script to isql → executes correctly

Cleanup

• Initialize $isql_flag = false explicitly for consistent boolean logic
• Fix deprecated curly brace string offset syntax ($cmd{n} → $cmd[n]) for PHP 7.4+

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Dynamic SQL Error SQL error code = -104 Token unknown - line 1, column 1 ^ </issue_title>
<issue_description>Hi,

I have problem with:

SET TERM ^ ;
CREATE OR ALTER trigger XXX_YYY0 for AAAAAAAA
active before delete position 0
AS
begin
  --something
end;^
SET TERM ; ^

Thanks!</issue_description>

<agent_instructions>seems to be a generic execute sql issue </agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Dynamic SQL Error SQL error code = -104 Token unknown - line 1, column 1 ^  #22

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.