judo-runtimedialect-extension

name: judo-runtime:dialect-extension description: Add support for new database dialects in JUDO DAO RDBMS. Use when integrating new databases like MySQL, Oracle, or custom RDBMS systems. metadata: author: BlackBelt Technology version: "${project.version}"

Dialect Extension

Guide for adding support for new database dialects in JUDO DAO RDBMS.

Dialect Architecture

flowchart TB
    subgraph "Dialect Layer"
        DI["Dialect Interface"]
        PG["PostgreSQL Dialect"]
        HS["HSQLDB Dialect"]
        CU["Custom Dialect"]
    end
    
    subgraph "Usage"
        DAO["RdbmsDAOImpl"]
        PM["RdbmsParameterMapper"]
        SE["StatementExecutor"]
    end
    
    DI --> PG
    DI --> HS
    DI --> CU
    DAO --> DI
    PM --> DI
    SE --> DI

Dialect Interface

The Dialect interface is minimal:

package hu.blackbelt.judo.runtime.core.dao.rdbms;

public interface Dialect {
    
    /**
     * Returns the dialect name (e.g., "postgresql", "hsqldb")
     */
    String getName();
    
    /**
     * Returns the dual table name for SELECT without FROM
     * (e.g., "DUAL" for Oracle, empty for PostgreSQL)
     */
    String getDualTable();
}

Creating a Custom Dialect

Step 1: Implement the Interface

package com.example.dialect;

import hu.blackbelt.judo.runtime.core.dao.rdbms.Dialect;

public class MySQLDialect implements Dialect {
    
    @Override
    public String getName() {
        return "mysql";
    }
    
    @Override
    public String getDualTable() {
        return "DUAL";
    }
}

Step 2: Create Dialect Provider

package com.example.dialect;

import hu.blackbelt.judo.runtime.core.dao.rdbms.Dialect;
import javax.inject.Provider;

public class MySQLDialectProvider implements Provider<Dialect> {
    
    @Override
    public Dialect get() {
        return new MySQLDialect();
    }
}

Step 3: Register with Guice

public class MySQLDialectModule extends AbstractModule {
    
    @Override
    protected void configure() {
        bind(Dialect.class).toProvider(MySQLDialectProvider.class);
    }
}

Database-Specific Considerations

Type Mapping

Override RdbmsParameterMapper for database-specific types:

public class MySQLParameterMapper extends DefaultRdbmsParameterMapper {
    
    @Override
    public int getSqlType(String targetDbType) {
        switch (targetDbType.toLowerCase()) {
            case "json":
                return Types.LONGVARCHAR; // MySQL JSON type
            case "tinyint":
                return Types.TINYINT;
            default:
                return super.getSqlType(targetDbType);
        }
    }
}

SQL Generation

Some dialects require custom SQL syntax:

RdbmsInit Implementation

For schema initialization:

public class MySQLRdbmsInit implements RdbmsInit {
    
    @Override
    public void execute(DataSource dataSource) {
        // MySQL-specific initialization
        try (Connection conn = dataSource.getConnection()) {
            // Set session variables, create functions, etc.
            conn.createStatement().execute(
                "SET sql_mode = 'STRICT_TRANS_TABLES'"
            );
        }
    }
}

Existing Dialect Modules

Testing Your Dialect

@Test
void testDialectConfiguration() {
    Dialect dialect = injector.getInstance(Dialect.class);
    
    assertThat(dialect.getName()).isEqualTo("mysql");
    assertThat(dialect.getDualTable()).isEqualTo("DUAL");
}

@Test
void testTypeMapping() {
    RdbmsParameterMapper mapper = injector.getInstance(RdbmsParameterMapper.class);
    
    assertThat(mapper.getSqlType("json")).isEqualTo(Types.LONGVARCHAR);
}

See Also

• agent-docs/extension-points.md - All extension interfaces
• /judo-runtime:query-debugging - Debug SQL issues