db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Gomes (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4338) Network client raises error "executeQuery method can not be used for update" when sql is preceded by /* */ comments
Date Wed, 05 Aug 2009 14:11:15 GMT
Network client raises error "executeQuery method can not be used for update" when sql is preceded
by /* */ comments
-------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-4338
                 URL: https://issues.apache.org/jira/browse/DERBY-4338
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.4.2.0
            Reporter: Will Gomes


Network derby client does not properly detect a sql select statement preceded by /* */ comments.
 As a result the sql appears to be detected as an update statement, and results in  the following
error:

 org.apache.derby.client.am.SqlException: executeQuery method can not be used for update.
	at org.apache.derby.client.am.Statement.checkForAppropriateSqlMode(Unknown Source)
	at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
	at org.apache.derby.client.am.PreparedStatement.executeQueryX(Unknown Source)

The problem appears to be in Statment.parseSqlAndSetSqlModes(), which only appears to check
for "--" style comments.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message