This is a reproducible example of <a class="issue-link js-issue-link" data-error-text=

I capture the error and stacktrace as following: <div class="snippet-clipboard-con

Query table of many DECIMAL columns causes error in terminal about rmysql HOT 5 OPEN

renkun-ken commented on July 26, 2024

Query table of many DECIMAL columns causes error in terminal

from rmysql.

Comments (5)

renkun-ken commented on July 26, 2024

I capture the error and stacktrace as following:

Available environments had calls:
1: source("R/test.R")
2: withVisible(eval(ei, envir))
3: eval(ei, envir)
4: eval(ei, envir)
5: test.R#6: dbGetQuery(con, "select * from test_table")
6: dbGetQuery(con, "select * from test_table")
7: dbSendQuery(conn, statement, ...)
8: dbSendQuery(conn, statement, ...)
9: .local(conn, statement, ...)
10: new("MySQLResult", Id = rsId)
11: initialize(value, ...)
12: initialize(value, ...)
13: validObject(.Object)
14: stop(msg, ": ", errors, domain = NA)
15: (function (e) 
{
    dump.frames(to.file = TRUE)
    browser()
})()

and I notice that in 9: .local(conn, statement, ...), rsId = c("names", "class") instead of an integer as supposed?

from rmysql.

renkun-ken commented on July 26, 2024

In the same session, when I create the connection and disconnect, and connect again, then the error disappears magically. But when multiple tables are queried, the error still occurs like the following:

Error in dbFetch(rs, n = -1, ...) : 
  INTEGER() can only be applied to a 'integer', not a 'list'
Calls: load_data -> sys.source -> eval -> eval
Error in .local(dbObj, ...) : 
  INTEGER() can only be applied to a 'integer', not a 'list'
Calls: load_data -> sys.source -> eval -> eval
Execution halted

from rmysql.