Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change test query to operate on BIGINT values #7610

Merged
merged 1 commit into from
Apr 16, 2021

Conversation

losipiuk
Copy link
Member

With previous query assertion was failing for connectors which exposed totalprice as
double value due to different double rounding behaviour in Trino and H2.

With previous  query assertion was failing for connectors which exposed totalprice as
double value due to different double rounding behaviour in Trino and H2.
@cla-bot cla-bot bot added the cla-signed label Apr 16, 2021
@losipiuk losipiuk requested a review from findepi April 16, 2021 09:08
@losipiuk
Copy link
Member Author

cc @findinpath

@@ -165,8 +165,8 @@ public void testLimit()
@Test
public void testLimitWithAggregation()
{
MaterializedResult actual = computeActual("SELECT custkey, SUM(CAST(totalprice * 100 AS BIGINT)) FROM orders GROUP BY custkey LIMIT 10");
MaterializedResult all = computeExpected("SELECT custkey, SUM(CAST(totalprice * 100 AS BIGINT)) FROM orders GROUP BY custkey", actual.getTypes());
MaterializedResult actual = computeActual("SELECT custkey, SUM(orderkey) FROM orders GROUP BY custkey LIMIT 10");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as long there is no casting of a double involved, it should works good.
thanks @losipiuk

@losipiuk losipiuk merged commit 270ef1c into trinodb:master Apr 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants