[
https://issues.apache.org/jira/browse/CALCITE-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898215#comment-15898215
]
Julian Hyde commented on CALCITE-1671:
--------------------------------------
On the mailing list you said you were working on a Go driver. Does Go have a
spec for how parameters are embedded in SQL? For example, what characters are
allowed in parameter names? Can a particular parameter be used more than once
in a query? If parameters are named, do they have an order?
That spec will determine whether this behavior enabled by default in Calcite's
parser or whether this feature will be on only if people specify a particular
parameter in the connect string.
> Support for named bind parameters
> ---------------------------------
>
> Key: CALCITE-1671
> URL: https://issues.apache.org/jira/browse/CALCITE-1671
> Project: Calcite
> Issue Type: New Feature
> Reporter: Francis Chuang
> Assignee: Julian Hyde
> Priority: Minor
>
> As discussed on the mailing list, there is some interest in supporting named
> bind parameters:
> {code}
> SELECT * FROM my_table WHERE my_column > :parameter1 AND mycolumn2 >
> :parameter2
> {code}
> Will mixing of named and unnamed parameters be allowed?
> {code}
> SELECT * FROM my_table WHERE my_column > :parameter1 AND mycolumn2 > ? AND
> mycolumn3 > :parameter3
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
