[
https://issues.apache.org/jira/browse/IGNITE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770003#comment-17770003
]
Pavel Pereslegin edited comment on IGNITE-20476 at 9/28/23 11:24 AM:
---------------------------------------------------------------------
[~jooger], thanks for the contribution!
Merged to the main branch
([56214b3|https://github.com/apache/ignite-3/commit/56214b3d1c14314fc870660016834b5a92bed2c9]).
was (Author: xtern):
[~jooger], thanks for the contribution.
Merged to the main branch
([56214b3|https://github.com/apache/ignite-3/commit/56214b3d1c14314fc870660016834b5a92bed2c9]).
> improve checking SQL exceptions in tests
> ----------------------------------------
>
> Key: IGNITE-20476
> URL: https://issues.apache.org/jira/browse/IGNITE-20476
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As of now there are few different approaches to check exception from
> SQLengine. It leads to hard control exceptions handling, like that all public
> Exception should be really public and don't belong to internal packages, or
> that all public exceptions have a text messages and so on.
> Let's move all exceptions checks related to SQL to two main points:
> 1) SqlTestUtils.assertThrowsSqlException(...) methods for SQL API
> 2) JdbcTestUtils.assertThrowsSqlException(...) methods fro JDBC API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
