Exit Codes

sql-splitter uses standard Unix exit codes.

Exit Codes

Code	Meaning	When
0	Success	Command completed without errors
1	Error	Runtime error (I/O, syntax, validation)
2	Invalid arguments	Bad CLI arguments

Usage in Scripts

Bash

#!/bin/bash
set -e  # Exit on error

sql-splitter validate dump.sql --strict
echo "Validation passed"

Or with explicit handling:

if sql-splitter validate dump.sql --strict; then
  echo "Valid"
else
  echo "Invalid"
  exit 1
fi

CI/CD

# GitHub Actions
- name: Validate
  run: sql-splitter validate dump.sql --strict
  # Fails step if exit code != 0

Validation Exit Codes

With --strict:

• Exit 0: No errors AND no warnings
• Exit 1: Errors or warnings present

Without --strict:

• Exit 0: No errors (warnings are ignored)
• Exit 1: Errors present

Checking Exit Codes

sql-splitter validate dump.sql --strict
EXIT_CODE=$?

case $EXIT_CODE in
  0)
    echo "Success"
    ;;
  1)
    echo "Validation failed"
    ;;
  2)
    echo "Invalid arguments"
    ;;
  *)
    echo "Unknown error: $EXIT_CODE"
    ;;
esac

JSON Output with Exit Codes

Single-file JSON output includes an error count in summary:

result=$(sql-splitter validate dump.sql --json)
errors=$(echo "$result" | jq -r '.summary.errors')

if [ "$errors" = "0" ]; then
  echo "Valid"
else
  echo "Invalid"
fi

In multi-file mode (glob input), each entry in results has a boolean passed field:

sql-splitter validate "backups/*.sql" --json | jq '.results[] | select(.passed | not) | .file'