michael-s-molina opened a new issue, #26133:
URL: https://github.com/apache/superset/issues/26133

   #### How to reproduce the bug
   Previously, it was possible to use a `bigint` column as a temporal column 
and create charts with it. Now, it's throwing an error and breaking some 
example charts.
   
   Error when opening the Video Games Sales dashboard:
   
   <img width="1776" alt="Screenshot 2023-11-29 at 11 05 37" 
src="https://github.com/apache/superset/assets/70410625/d2ce2fd0-5e6f-414d-adab-ac59ef30a346";>
   
   Error thrown when using `year`, which is a `bigint`, as a temporal column on 
SQLite:
   
   <img width="1756" alt="Screenshot 2023-11-29 at 10 55 10" 
src="https://github.com/apache/superset/assets/70410625/927b46b5-da32-4032-8d65-d751dca24268";>
   
   Error thrown when using `year`, which is a `bigint`, as a temporal column on 
Postgres:
   
   <img width="1762" alt="Screenshot 2023-11-29 at 10 56 52" 
src="https://github.com/apache/superset/assets/70410625/8508b0fc-b226-436b-a504-1b0b34724c7e";>
   
   ### Environment
   
   - superset version: `master`
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   Add any other context about the problem here.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to