I would support it as long as it doesn’t break people who wish to continue to use regular parameters. Try to find a specification (syntax) used in several other databases. Describe how the named parameters could be described and bound via JDBC (or minimal extensions to it). Then log a jira case for further discussion.
On May 15, 2026, at 7:56 AM, Jerome Haltom <[email protected]> wrote: > > Is there any interest in the parser to introduce the concept of named > parameters, or does it already exist somewhere? SqlDynamicParam right now is > indexed. This maps pretty cleanly to JDBC, and also ODBC, but plenty of > database types use named parameters now: @P1, etc. > > I am trying to wrap Calcite in a ORM framework which currently completely > loses track of the order of parameters it creates, since it expects the > underlying database itself to support named parameters. So, I have two > options of attack: fix that ORM framework, or find/add such a capability in > Calcite. > >
