datetime format and database expression on column level #652
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 'string3': ['%Y/%m/%d%H:%M:%S.%f', None], | ||
| } | ||
| for col in obj.table_columns: | ||
| print(col.column_name) |
|
Nice. This is looking solid. I'm going to test it against our production DB when I have a moment and report back. |
|
Ok. Everything looks good. This was pretty tricky but I think we support most use cases at this point. Thanks for bearing with me. |
|
Thanks for you patience for showing me the right way to write python code! I haven't fix those small issues you just pointed out. You will do it yourself? |
|
Those were pretty minor. Submit a PR if you feel like it, otherwise we'll get to it at some point. |
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this pull request
Nov 17, 2021
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this pull request
Nov 24, 2021
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this pull request
Nov 25, 2021
zhaoyongjie
pushed a commit
to zhaoyongjie/incubator-superset
that referenced
this pull request
Nov 26, 2021
john-bodley
added a commit
that referenced
this pull request
Jan 12, 2022
* fix: Workaround for sqlparse issue #652 * Update superset/sql_parse.py Co-authored-by: Ville Brofeldt <[email protected]> * Update sql_parse.py Co-authored-by: John Bodley <[email protected]> Co-authored-by: Ville Brofeldt <[email protected]>
shcoderAlex
pushed a commit
to casual-precision/superset
that referenced
this pull request
Feb 7, 2022
* fix: Workaround for sqlparse issue apache#652 * Update superset/sql_parse.py Co-authored-by: Ville Brofeldt <[email protected]> * Update sql_parse.py Co-authored-by: John Bodley <[email protected]> Co-authored-by: Ville Brofeldt <[email protected]>
bwang221
pushed a commit
to casual-precision/superset
that referenced
this pull request
Feb 10, 2022
* fix: Workaround for sqlparse issue apache#652 * Update superset/sql_parse.py Co-authored-by: Ville Brofeldt <[email protected]> * Update sql_parse.py Co-authored-by: John Bodley <[email protected]> Co-authored-by: Ville Brofeldt <[email protected]>
mistercrunch
added
🏷️ bot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a revision of #506 .
Now users can edit datetime format and database expression per column. Without specifying anything, Caravel follows default pandas timestamp format and empty database_expression.
If timestamp is stored in epoch format in Integer type, users should input this:
If it is stored in date/timestamp type, such as
timestamp with time zonein postgres, users should input this:Query constructed by Caravel looks like this: