pvergain commented on issue #15768:
URL: https://github.com/apache/superset/issues/15768#issuecomment-987887089


   > > I can replicate this issue using a fresh install of the latest docker 
image per the instructions 
[here](https://superset.apache.org/docs/installation/installing-superset-using-docker-compose).
   > > Screenshot below.
   > > 
![superset_issue_15768](https://user-images.githubusercontent.com/44637027/130059441-b59e7cfa-42d6-4304-9bba-8d2084a02415.png)
   > > According to a pip freeze in the app container (superset_app), this 
version is using psycopg2 v. 2.9.1.
   > > Manually replacing version 2.9.1 with 2.8.6 as suggested above resolves 
the issue.
   > > @mail2lawi's solution above (time at time zone 'CEST')... also was an 
effective fix, leading me to support the hypothesis that this issue is 
specifically related to columns which contain timestamptz values.
   > > Thank you for your help all!
   > 
   > Hi @jonathanStrange0 , I'm new to superset. How do you change the version, 
I cloned master and found `["psycopg2-binary==2.8.5"` as a dependency. This 
version appears to be older than 2.8.6 and I get the same error.
   > 
   > What are the steps to change the version with docker-compose. Thank you 
very much.
   
   Hi !
   
   For docker-compose-non-dev, here is my "hack":
   
   ```
       docker-compose -f docker-compose-non-dev.yml up
       docker-compose -f docker-compose-non-dev.yml exec superset pip uninstall 
-y psycopg2-binary
       docker-compose -f docker-compose-non-dev.yml exec superset pip install 
psycopg2-binary==2.8.6
       docker-compose -f docker-compose-non-dev.yml restart superset
   ```
   
   Before the hack
   ==============
   
   
![image](https://user-images.githubusercontent.com/57228/145030199-b5b3e03e-e45f-4196-9a29-15ea70c73fb2.png)
   
   After the hack
   ==============
   
   
![image](https://user-images.githubusercontent.com/57228/145030265-0a2c9f15-8d7f-47a6-bca3-cfd4cb5ea064.png)
   
   
   
   
   


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