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

Indent issue with named function column in select #10

Closed
andialbrecht opened this issue Apr 18, 2012 · 2 comments
Closed

Indent issue with named function column in select #10

andialbrecht opened this issue Apr 18, 2012 · 2 comments
Labels
Milestone

Comments

@andialbrecht
Copy link
Owner

_This is a _shadow issue* for Issue 10 on Google Code (from which this project was moved).
Added 2010-01-08T15:12:13.000Z by paul.bridger.
Labels: Type-Defect, Priority-Medium.
Please make updates to the bug there.*

Original description

v0.1.1
Using reindent = True

At some stage I'll dig into the code to find the problem here, but if
someone fixes it before I get around to it that would be wonderful. :)

Formatted SQL is:

SELECT SERIAL# SERIAL,
       SERVICE_NAME SERVICE_NAME,
       P1 WAIT_P1,
       P2 WAIT_P2,
       P3 WAIT_P3,
       ROW_WAIT_ROW# ROW_WAIT_ROW,
       ROW_WAIT_OBJ# ROW_WAIT_OBJ,
       ROW_WAIT_BLOCK# ROW_WAIT_BLOCK,
       ROW_WAIT_FILE# ROW_WAIT_FILE,
       DECODE(STATE,'WAITING',
                    'WAITING',
                    'ON CPU') WAIT_STATE,
                              DECODE(STATE,'WAITING',
                                           WAIT_CLASS,
                                           'ON CPU') WAIT_CLASS,
                                                     DECODE(STATE,'WAITING',
                                                                  EVENT,
                                                                  'ON CPU')
WAIT_EVENT, SID SID, AUDSID AUDSID, USERNAME USERNAME, MACHINE MACHINE,
CLIENT_IDENTIFIER CLIENT_IDENTIFIER, COMMAND COMMAND, STATUS STATUS,
PROCESS PROCESS, PROGRAM PROGRAM, TYPE TYPE, CLIENT_INFO CLIENT_INFO,



                                     SQL_HASH_VALUE SQL_HASH_VALUE,



                                     SQL_ID SQL_ID,



                                     PLAN_HASH_VALUE PLAN_HASH_VALUE,



                                     MODULE MODULE,



                                     ACTION ACTION,



                                     LOGON_TIME LOGON_TIME,



                                     LAST_CALL_ET LAST_CALL_ET,



                                     FIXED_TABLE_SEQUENCE FIXED_TABLE_SEQUENCE,



                                     WAIT_CLASS WAIT_CLASS,



                                     SECONDS_IN_WAIT SECONDS_IN_WAIT,



                                     WAIT_TIME WAIT_TIME,



                                     PLSQL_ENTRY_OBJECT_ID
PLSQL_ENTRY_OBJECT_ID,



                                     PLSQL_ENTRY_SUBPROGRAM_ID
PLSQL_ENTRY_SUBPROGRAM_ID,



                                     PLSQL_OBJECT_ID PLSQ
@andialbrecht
Copy link
Owner Author

Moving this issue to 0.1.7 to get 0.1.6 released. I took a first glance at it, but couldn't figure out the problem behind it. My first guess was, that the # causes some troubles, but that isn't the case. The given example seems to be incomplete, but this shouldn't cause the problems (hey, we don't validate :) )

@andialbrecht
Copy link
Owner Author

We still have some problems with this SQL dialect, especially the # sign causes some troubles. I need some insight what the SERIAL# actually means.

ovr pushed a commit to cube-js/sqlparse that referenced this issue Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant