Fix MSSQL import of exported scripts

[yzxcj797]

Summary

Scripts exported from the MSSQL generator could not be imported again. Two parser-boundary cases caused the failure:

• a semicolon-terminated statement followed by a GO batch separator;
• ALTER TABLE ... ADD FOREIGN KEY, which the current transactsql grammar in node-sql-parser does not support.

MSSQL import now normalizes GO batches into statement separators before parsing. Foreign-key ALTER statements are extracted, converted to the equivalent MySQL ALTER syntax accepted by the parser, and converted back into the AST shape fromMSSQL already consumes. Named constraints, schema-qualified tables, quoted identifiers, composite column lists, referential actions, scripts without semicolons, and single-statement inputs are covered.

Fixes #320.

Testing

• npm test — 8/8 tests pass
• npm run lint — passes with zero warnings
• npm run build — passes (existing lottie-web eval and large-chunk warnings remain)
• git diff --check — passes
• The development server starts successfully with the modified import path.

The new tests cover exported-style table/FK round trips, GO with and without semicolons, named constraints, ON UPDATE/ON DELETE actions, extended-property EXEC batches, no-GO input, single non-terminated statements, and multi-line foreign-key column lists.

[vercel]

@yzxcj797 is attempting to deploy a commit to the dottle's projects Team on Vercel.

A member of the Team first needs to authorize it.