[
https://issues.apache.org/jira/browse/IGNITE-27732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-27732:
------------------------------------
Description:
IGNITE-25403 introduced overloads without tx to the SQL API. Some of those
overloads are problematic:
* Break existing code
* Difficult to use in the new code
The following code does not compile:
{code}
execute(null, statement);
{code}
Error:
{code}
java: reference to execute is ambiguous
both method execute(java.lang.String,java.lang.Object...) in
org.apache.ignite.sql.IgniteSql and method
execute(org.apache.ignite.tx.Transaction,org.apache.ignite.sql.Statement,java.lang.Object...)
in org.apache.ignite.sql.IgniteSql match
{code}
Problematic methods:
{code}
execute(String, Object...)
executeAsync(String, Object...)
{code}
We wanted to make the life easier for the user, but those two methods make it
harder.
was:
IGNITE-25403 introduced overloads without tx to the SQL API. Some of those
overloads are problematic:
* Break existing code
* Difficult to use in the new code
The following code does not compile:
{code}
execute(null, statement);
{code}
Error:
{code}
java: reference to execute is ambiguous
both method execute(java.lang.String,java.lang.Object...) in
org.apache.ignite.sql.IgniteSql and method
execute(org.apache.ignite.tx.Transaction,org.apache.ignite.sql.Statement,java.lang.Object...)
in org.apache.ignite.sql.IgniteSql match
{code}
Problematic methods:
{code}
execute(String, Object...)
executeAsync(String, Object...)
{code}
> SQL API: reference to execute is ambiguous
> ------------------------------------------
>
> Key: IGNITE-27732
> URL: https://issues.apache.org/jira/browse/IGNITE-27732
> Project: Ignite
> Issue Type: Bug
> Components: sql ai3
> Affects Versions: 3.2
> Reporter: Pavel Tupitsyn
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.2
>
>
> IGNITE-25403 introduced overloads without tx to the SQL API. Some of those
> overloads are problematic:
> * Break existing code
> * Difficult to use in the new code
> The following code does not compile:
> {code}
> execute(null, statement);
> {code}
> Error:
> {code}
> java: reference to execute is ambiguous
> both method execute(java.lang.String,java.lang.Object...) in
> org.apache.ignite.sql.IgniteSql and method
> execute(org.apache.ignite.tx.Transaction,org.apache.ignite.sql.Statement,java.lang.Object...)
> in org.apache.ignite.sql.IgniteSql match
> {code}
> Problematic methods:
> {code}
> execute(String, Object...)
> executeAsync(String, Object...)
> {code}
> We wanted to make the life easier for the user, but those two methods make it
> harder.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
