Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi everyone! I have been using an ODBC connector to access my data in Trino. Suddenly, it stopped working with the attached error message.
I don't know why this error message appeared suddenly on a working connection already established and daily refreshed. I can change the date type of my columns that use timestamp(6) to date, or timestamp(0), but is impracticable on this moment.
Any suggestion of what could I do?
Hi!
The column "date" has a datetype "timestamp(6)" for a long time, and this not has been changed. No changes on data in Trino were made. My driver (treasure data presto odbc) is updated.
Hey @dpontes ,
This is a tough one - is it possible that you ahve some NON-date data in one of the fields (an extra space, an odd character, etc). These are really tough to find but I have had that experience before in a SQL query.... Or, you could ask the Presto folks if they are seeing this issue or having other reports of a problem.
Proud to be a Datanaut!
Private message me for consulting or training needs.
Hi ,
This appears to me that this is coming from the Presto database itself. In this Presto list (Data Types — Presto 0.278.1 Documentation (prestodb.io)) I am wondering if you are using the Timesta...
I know that Power BI won't accept text in a Date or Date/Time field. Perhaps the output data changed as well since you say that this is more current?
Proud to be a Datanaut!
Private message me for consulting or training needs.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!