You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a BIGINT column is coerced into integer in R, RPresto churns out a generic warning message
library(RPresto)
library(DBI)
conn<-RPresto::presto_default()
dbGetQuery(conn, "SELECT CAST(POW(2, 31) AS BIGINT) AS bigint_overflow")
#> Warning in as.integer.integer64(x): NAs produced by integer overflow#> # A tibble: 1 × 1#> bigint_overflow#> <int>#> 1 NA
This warning message is produced by bit64::as.integer.integer64().
In a dummy example like the one above, it's trivial to figure out which column causes the overflow. But in a table with significantly more columns, it could be difficult to figure out which one is the culprit and needs attention. We should give the overflow warning with the offending column name, so it's easier for the user to troubleshoot and deal with the warning.
The text was updated successfully, but these errors were encountered:
Currently when a
BIGINT
column is coerced intointeger
in R, RPresto churns out a generic warning messageCreated on 2022-09-29 with reprex v2.0.2
This warning message is produced by
bit64::as.integer.integer64()
.In a dummy example like the one above, it's trivial to figure out which column causes the overflow. But in a table with significantly more columns, it could be difficult to figure out which one is the culprit and needs attention. We should give the overflow warning with the offending column name, so it's easier for the user to troubleshoot and deal with the warning.
The text was updated successfully, but these errors were encountered: