Troubleshooting

Solutions to common issues with database connections, schema validation, and runtime execution in an5 ORM.

Active Context: Troubleshooting for Swift on Postgresql.

Connection Issues

1. Connection Refused or Host Unreachable

Symptom: ECONNREFUSED, Connection refused, or timeout trying to open database connection.

Diagnostic Checklist:

  1. Confirm the database service is running on the host and port.
  2. Verify network firewalls allow incoming traffic from your application IP.
  3. Validate connection string syntax for Postgresql:
# Valid connection format for Postgresql
DATABASE_URL=postgres://user:password@localhost:5432/dbname?sslmode=disable

PostgreSQL specific notes:

  • Check pg_hba.conf allows connections from your client IP.
  • When connecting to cloud instances (RDS, Supabase, Neon), append ?sslmode=require.
  • If vector queries fail, ensure extension is enabled: CREATE EXTENSION IF NOT EXISTS vector;.

Connection Diagnostic Test

Run a quick connection health test using your active language:


Schema & Code Generation Issues

1. Type Mismatch in Schema

Error: Invalid field type 'X' for provider 'Y'

Cause: The schema .an5 uses a type specific to another database dialect (e.g. BIT on SQLite or BOOLEAN on SQL Server).

Solution: Align field types in an5Schema/ with the dialect rules of Postgresql:

  • Consult the Field Types reference for valid types per provider.

2. Output Directory Not Found

Error: Directory does not exist for generator output

Solution: an5Orm generates directories automatically. Ensure your user has filesystem write permissions in the workspace and verify outputs paths in an5Orm.config.js.


Next Steps