-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Issue using type datetime or time #1900
Comments
The second traceback should be handled by this:
|
Namely datetime.time and numpy.bool_ Refs: apache#1900 Refs: apache#1903
Namely datetime.time and numpy.bool_ Refs: apache#1900 Refs: apache#1903
@nypgand1 latest master should work for you for the second backtrace, regarding the first one if you can add some prints and sort out what arg1 and arg2 it would be helpful. Let us know! |
@xrmx Thank you so much! |
As noted in #1929, i get the same error as the first traceback above. Appears that postgres has two different timestamp column types Here's the arg1 and arg2 passed into the
I just tried selecting only the timestamp column, and got a different trace:
|
Anyone have any idea how to fix this issue with |
Closing, should be fixed by #1907 |
@mistercrunch Should we open a second bug for the first stack trace? It is still affecting me.
This is using a very recent version built from git:
|
@mschulkind per #1900 (comment) it's not the stacktrace that is needed but the actual types. Are yours the very same of #1900 (comment) ? |
Yes, it is exactly the same type. Looks like this is an even more specific bug that could be reopened: |
Namely datetime.time and numpy.bool_ Refs: apache#1900 Refs: apache#1903
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
superset==0.14.1
psycopg2==2.6.2
python-3.4.1 on heroku
heroku-postgresql 9.6.1
Actual results
If I use type
datetime
field and query, I got an error that says datetime can not be understood by numpy. Maybe it cause by typetimestamp
in postgresql?If I split it into 2 fields (type
date
&time
) and query, I got an error that says datetime.time object can not be serializable. Cause in methodjson_iso_dttm_ser()
, it deals with typedatetime
ordate
only, so i think using typetimedelta
(typeinterval
in postgresql) will be the same case.The text was updated successfully, but these errors were encountered: