[ https://forge.continuent.org/jira/browse/SEQUOIA-846?page=all ]
Emmanuel Cecchet resolved SEQUOIA-846:
--------------------------------------
Assign To: Mathieu Peltier (was: Emmanuel Cecchet)
Resolution: Fixed
Fixed in 2.10 and 3.0
Might want to add a test for this before closing
> SELECT parser can fail to parse subselects or multistatement SELECTs
> --------------------------------------------------------------------
>
> Key: SEQUOIA-846
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-846
> Project: Sequoia
> Type: Bug
> Components: Core
> Versions: Sequoia 3.0 beta1, Sequoia 2.10.2
> Reporter: Emmanuel Cecchet
> Assignee: Mathieu Peltier
> Fix For: Sequoia 2.10.3, Sequoia 3.0
>
>
> SELECT request parser tries to look for subselects to extract all table
> names. If subselect parsing fails, the fallback mechanism in the catch block
> returns an unaliased list of tables which will cause a ClassCastException
> later on.
> Note that in Sequoia 3.0, the SemanticManager is not set on the subselect
> request which will cause subselect parsing to systematically fail.
> Additionally the Sequoia SQL console tries to send multistatement SELECTs
> through executeQuery (which is not correct) but cause the parser to fail (try
> statement.executeQuery("SELECT * from foo ; SELECT * FROM foo").
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
