Skip to content

[automatic failover] Missing support for clientOptions per Database #3572

@ggivo

Description

@ggivo

Bug Report

Missing support for using different ClientOptions per database in MultiDbClient connections

Current Behavior
MultiDbClient currently applies the same ClientOptions instance when connecting to all configured databases, preventing per-database customization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions