DLoc-poste opened a new issue, #30361:
URL: https://github.com/apache/superset/issues/30361

   ### Bug description
   
   Hello,
   From postgressql database version : 9.6.16 :  
   Some date fields are displayed correctly in SQL request but are not 
displayed correctly in superset
   
   I found the issue below but it is closed : 
   
![image](https://github.com/user-attachments/assets/e132d560-5363-4efb-be62-f80400226dc8)
   
   
   
   ### How to reproduce the bug
   
   - In postgresql database version : 9.6.16 , in a date field , insert a value 
before may before 1936 : 
   10/01/1901 
   - display it in a superset 4.0.2 dashboard. 
   
   ### Screenshots/recordings
   
   **From database request :** 
   ![From 
databse](https://github.com/user-attachments/assets/bb541047-48c6-45ae-a62f-7676814a1df5)
   
   **From superset dashboard :**
   ![from 
superset](https://github.com/user-attachments/assets/08876fd9-03bb-4aa3-b1d4-41949d17478a)
   
   **From superset some well displayed :** 
   ![from superset some 
ok](https://github.com/user-attachments/assets/8d3c5b3f-0c2f-42d3-a57f-f9fc2cdcae50)
   
   **database field definition :**
   
![2024-09-23_15h30_33](https://github.com/user-attachments/assets/3bc29f55-171b-40ae-b01a-33181503fc89)
   
   
   ### Superset version
   
   4.0.2
   
   ### Python version
   
   I don't know
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Firefox
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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