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
Note that the errors, while similar, are different: interface conversion: interface {} is []uint8, not string vs interface conversion: interface {} is string, not []uint8
The text was updated successfully, but these errors were encountered:
So the reason for the failure makes sense: the BLOB type mirrors MySQL's BLOB type and maxes out at 65536 bytes. For longer blobs, we have the MEDIUMBLOB and LARGEBLOB types.
However, this should be an error, not a panic.
Oddly, as of today I'm unable to reproduce the panic on my dev machine with the above repro steps, instead getting the appropriate error.
My windows machine where I first discovered the panic can still reproduce it. Both machines have the same version installed. I'm not yet sure why this changed.
Depending on the exact method used, we can get two different stack traces and error messages.
Method 1:
LOAD_FILE
repro steps:
error:
interface conversion: interface {} is []uint8, not string
Stack trace:
Method 2: inline file in query
repro.py:
error:
interface conversion: interface {} is string, not []uint8
stack trace:
Note that the errors, while similar, are different:
interface conversion: interface {} is []uint8, not string
vsinterface conversion: interface {} is string, not []uint8
The text was updated successfully, but these errors were encountered: