Skip to content

Support database connections where prepared statements are unsupported #283

@LouisGariepy

Description

@LouisGariepy

Migrated from halcyonnouveau/clorinde#256, originally reported by @Destructor17 on 2026-05-08.

Describe the problem

Code generated by this crate relies on support of prepared statements because many methods in tokio-postgres use prepared statements just to determine types of parameters. For example Cloudflare Hyperdrive seem to use statement-level pooling, while preparation and execution are 2 different statements, so I just keep catching database errors.

Describe the solution you'd like

Actually I implemented my own solution in halcyonnouveau#255. This issue is needed in case if original PR is rejected or becomes stale

Alternatives considered

No response

Additional context

No response

Importance

I cannot use Clorinde without it

Metadata

Metadata

Assignees

No one assigned

    Labels

    codegenAn issue regarding code generation, or the generated code itself.featureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions