Troubleshooting

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

Active Context: Troubleshooting for Dotnet on Mysql.

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 Mysql:
# Valid connection format for Mysql
DATABASE_URL=mysql://user:password@localhost:3306/mydb

MySQL specific notes:

  • If connecting with MySQL 8 caching_sha2_password, ensure the client driver supports modern auth or alter user to mysql_native_password.

Connection Diagnostic Test

Run a quick connection health test using your active language:

using System;
using an5Adapters.Dotnet;

try {
    var adapter = new An5Adapter(Environment.GetEnvironmentVariable("DATABASE_URL")!);
    Console.WriteLine("Connected successfully to Mysql");
} catch (Exception ex) {
    Console.WriteLine($"Connection failed: {ex.Message}");
}

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 Mysql:

  • 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