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
Describe the problem
Code generated by this crate relies on support of prepared statements because many methods in
tokio-postgresuse 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