Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Type mismatch for INTERVAL
See original GitHub issuepgtyped generates string type for INTERVAL values
But in runtime the value is PostgresInterval object
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error: Type mismatch for column because of INTERVAL #4854
DB::Exception: Type mismatch for column tmin. Column has type AggregateFunction(min, DateTime), got type AggregateFunction(min, DateTime('UTC')) ...
Read more >cannot resolve column due to data type mismatch PySpark
I am trying to create a view based on a few of these levels within the json data. Update: Duplicating token df.selectExpr('result_set.currency', ...
Read more >type mismatch error without string and numeric variables?
Hi all, Here is what I am hoping is an easy issue to solve. I want to use strmst2 to calculate restricted mean...
Read more >Type Mismatch Error! | MrExcel Message Board
I can't seem to find where the type mismatch occurs. ... Dim KOP As Integer Dim Build As Double Dim Interval As Integer...
Read more >pyspark.sql.utils.AnalysisException: cannot resolve 'xx' due to ...
pyspark.sql.utils.AnalysisException: cannot resolve 'xx' due to data type mismatch: differing types in 'xx' (double and interval).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@silasdavis my problem is that I have a nullable
INTERVALcolumn.Selecting it as-is generates
string | nullbut returnsPostgresInterval | nullin runtime Selecting it ascolumn::TEXTgeneratesstringbut returnsstring | nullin runtimethat’s the current situation
Thanks @meoyawn! This requires the runtime layer. Tracking this here #148