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

Wrong parse with OrderBy Cause #7

Closed
zhanzecheng opened this issue Oct 23, 2018 · 2 comments
Closed

Wrong parse with OrderBy Cause #7

zhanzecheng opened this issue Oct 23, 2018 · 2 comments

Comments

@zhanzecheng
Copy link

Hi Tao,
I find a incorrect parse example as below. The limit and orderBy are all None.
SQL : {u'orderBy': [], u'from': {u'table_units': [[u'table_unit', 1], [u'table_unit', 2]], u'conds': [[False, 2, [0, [0, 5, False], None], [0, 13, False], None]]}, u'union': None, u'except': None, u'having': [[False, 4, [0, [0, 16, False], None], 2010.0, None]], u'limit': None, u'intersect': None, u'where': [], u'groupBy': [[0, 13, False]], u'select': [False, [[0, [0, [0, 8, False], None]]]]}
query : SELECT T1.Area FROM APPELLATIONS AS T1 JOIN WINE AS T2 ON T1.Appelation = T2.Appelation GROUP BY T2.Appelation HAVING T2.year < 2010 ORDER BY count(*) DESC LIMIT 1
Thanks,
Zecheng

@taoyds
Copy link
Owner

taoyds commented Oct 25, 2018

Hi Zecheng,

please check out #3.

Best,
Tao

@zhanzecheng
Copy link
Author

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants