[ https://forge.continuent.org/jira/browse/SEQUOIA-1095?page=comments#action_14544 ]
Emmanuel Cecchet commented on SEQUOIA-1095: ------------------------------------------- Whereas the 2 first scenarios generate an internal error in Sequoia, it looks like the last one is an error generated by the backend (in which case the transparency is ok there). Is that correct? Is the behavior any different if the same query is executed using executeQuery or executeUpdate? Is the problem similar with CallableStatements? Regarding '--' do we have to parse to see if there is something like '-- some comment\nSELECT FROM t...' and execute if this is not empty? > Comments-only statements throw error "ResultSet is from UPDATE. No Data." > ------------------------------------------------------------------------- > > Key: SEQUOIA-1095 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-1095 > Project: Sequoia > Type: Bug > Components: Core > Reporter: Gilles Rayrat > Assignee: Gilles Rayrat > Fix For: sequoia 2.10.11, Sequoia 4.0 > > > When issuing a statement that only contains a comment (either "/* ... */" or > "-- .."), the following error is returned: > Error while building Sequoia ResultSet (ResultSet is from UPDATE. No Data.) > Note that -- is SQL92 standard, and /* */ is SQL99, so these should be > supported -- 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
