prestodb/presto-go-client

"unknown" column types cause errors

sirwart opened this issue · 2 comments

You can get an unknown column type by running the query select null;. Instead of being able to scan these into a string the driver returns an error, even though it's a valid query. I fixed it by including in the switch statement with the other character types, although I'm not sure that's the right fix.

With that fix you should run the unit and e2e tests, and assume good if they pass. Give it a shot.

Landed in #22

Thanks!