I have also been struggling with this issue for several months. However, I have come across a solution that may help you as well.
In a nutshell, the issue occurs when certain text columns do not appear after integer/numeric columns. When the columns are not aligned properly in the query, an error of invalid index
is thrown and your connection may freeze. The issue then is, how do I know what to put at the end of my query?
To determine this, one could typically examine a column using class()
or typeof()
. To examine such information from the database, you can use a query such as:
dbColumnInfo(dbSendQuery(con, "SELECT * from schema.table")) # You may not require the schema part...
This will return a table with a type field for every column in the data-set of interest. You can then use this table as an index to sort the select()
statement. My particular difficulty is that the type
field in the table was all numbers! However, I noticed that every column with a negative number, when placed at the end of the select statement, fixed my query and I could pull the whole table just fine. For example, my full solution:
# Create my index of column types (ref to the current order)
index <- dbColumnInfo(dbSendQuery(con, "SELECT * from schema.table"))
index$type <- as.integer(index$type) # B/c they are + and - numbers!
# Create the ref to the table
mySQLTbl <- tbl(con, in_schema("schema", "tablename"))
# Use the select statement to put all the + numbered columns first!
mySQLTbl %>%
select(c(which(index$type>=0),
which(index$type<0)))
As for reason for why this occurs, I am not sure and I do not have the data access privileges to dig much deeper in my use-case
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…