Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TimeZone in MySQL queries #6490

Closed
squalou opened this issue Dec 5, 2018 · 1 comment
Closed

TimeZone in MySQL queries #6490

squalou opened this issue Dec 5, 2018 · 1 comment
Labels
change:backend Requires changing the backend inactive Inactive for >= 30 days v0.28

Comments

@squalou
Copy link

squalou commented Dec 5, 2018

Hi,

I'm using superset against a MySQL databases, where data are stored in UTC (which is fine).
Clients connections to these databases all have the parameter ?serverTimeZone=XX/YY

I didn't find the equivalent in superset.

When I tried to add the parameter in SqlAlchemy URI, it told me 'serverTimeZone is an invalid keyword argument'

I've seen #703 which is related but apparently for Druid.

Superset version

0.28.1

Expected results

in SQL Editor, run this query against a mysql database is a different timezone :

select now();

get local time as result

Actual results

UTC time is returned

@kristw kristw added #question change:backend Requires changing the backend v0.28 labels Dec 7, 2018
@stale
Copy link

stale bot commented Apr 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 10, 2019
@stale stale bot closed this as completed Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change:backend Requires changing the backend inactive Inactive for >= 30 days v0.28
Projects
None yet
Development

No branches or pull requests

2 participants