Skip to content

Conversation

@tanclary
Copy link

As detailed in looker-open-source/calcite#45, we should cast STRINGs to FLOAT64 before casting them to INTEGERs to avoid errors with decimals. This means the whole part of the result is sometimes differs from the original string.

As detailed in looker-open-source/calcite#45, we should cast STRINGs to FLOAT64 before casting them to INTEGERs to avoid errors with decimals. This means the whole part of the result is sometimes differs from the original string.
Copy link

@Anthrino Anthrino left a comment

Choose a reason for hiding this comment

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

LGTM, might be good to revert this once root cause is fixed.

@tanclary
Copy link
Author

LGTM, might be good to revert this once root cause is fixed.

The root cause is just that BigQuery doesn't allow it, nothing on our end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants