Mailing-List: contact dev-help@calcite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@calcite.apache.org
From: Julian Hyde <jhyde@apache.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Are named parameters supported in Calcite?
Date: Mon, 6 Mar 2017 11:29:47 -0800
References: <2ba12dac-1f7d-14cf-ef92-298f3d5bb801@gmail.com>
To: dev@calcite.apache.org
In-Reply-To: <2ba12dac-1f7d-14cf-ef92-298f3d5bb801@gmail.com>
Message-Id: <CC7AC4E7-3450-4644-96AC-7287D53DDC64@apache.org>
archived-at: Mon, 06 Mar 2017 19:30:01 -0000

Calcite/Avatica does not support named parameters because as far as I =
know JDBC and ODBC do not.

I am open to the idea of supporting them. I think it would require =
changes to both Calcite (for the parser & parameter metadata) and =
Avatica (adding name to parameter metadata).

Can you create a JIRA case, including a specification for how these work =
such as the SQL syntax for named parameters.

Julian


> On Mar 5, 2017, at 2:03 AM, F21 <f21.groups@gmail.com> wrote:
>=20
> Hello all,
>=20
> Go 1.8 has been released recently and it introduces some new features =
and interfaces for the database/sql package which I maintain the Go =
avatica driver for. I am currently working on introducing these new =
features to the Go driver.
>=20
> One of the new features in Go 1.8 is support for named parameters:
>=20
> SELECT * FROM my_table WHERE my_column > :parameter1 AND mycolumn2 > =
:parameter2
>=20
> Implementation of named parameter is optional for cases where they are =
not supported. I've search JIRA as well as language reference here: =
https://calcite.apache.org/docs/reference.html
>=20
> =46rom my understanding, this does not appear to be supported in =
Calcite, but it would be cool if this can be confirmed :)
>=20
> Cheers,
>=20
> Francis
>=20