Previously, the importer rejected these scripts because it couldn’t handle custom statement delimiters.

The updated parser identifies the complete procedure as a single statement before passing it to the native MySQL connection.

I tested the parser with Swift, including a stored procedure containing multiple SQL statements. The parser test passed. However, I haven’t compiled the complete macOS application or tested importing against a live MySQL server.

build/Build/Intermediates.noindex/WorkbenchReplacement.build/Debug/WorkbenchReplacement.build/Objects-normal/arm64/MainView.stringsdata

@@ -540,7 +540,7 @@
       },
       {
         "comment": "",
-        "key": "Supports ordinary SQL statements. Dumps using custom DELIMITER directives or stored routines are not supported yet.",
+        "key": "Supports MySQL DELIMITER directives, triggers and stored routines. Import is not transactional; use a verified backup before restoring.",
         "location": {
           "startingColumn": 30,
           "startingLine": 1687

build/Build/Intermediates.noindex/XCBuildData/registered-launchservices.txt

@@ -9,3 +9,4 @@
 /Volumes/Developer/Applications/WorkbenchReplacement/build/Build/Products/Debug/WorkbenchReplacement.app
 /Volumes/Developer/Applications/WorkbenchReplacement/build/Build/Products/Debug/WorkbenchReplacement.app
 /Volumes/Developer/Applications/WorkbenchReplacement/build/Build/Products/Debug/WorkbenchReplacement.app
+/Volumes/Developer/Applications/WorkbenchReplacement/build/Build/Products/Debug/WorkbenchReplacement.app

build/Build/Products/Debug/WorkbenchReplacement.app/Contents/_CodeSignature/CodeResources

@@ -19,7 +19,7 @@
 		<dict>
 			<key>cdhash</key>
 			<data>
-			Iv3+eGn5ABjizzuIQDv3FNnVrWE=
+			cNkEGkXY0XL0979Pg1Y/5+wqs/g=
 			</data>
 			<key>requirement</key>
 			<string>identifier "WorkbenchReplacement.debug" and anchor apple generic and certificate leaf[subject.CN] = "Apple Development: Mark Gregory (FLBRJ3BYDD)" and certificate 1[field.1.2.840.113635.100.6.2.1] /* exists */</string>