[DERBY-4338] Network client raises error "executeQuery method can not be used for update" when sql is preceded by /* */ comments

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0
• Fix Version/s: 10.4.2.1, 10.5.3.1, 10.6.1.0
• Component/s: Network Client
• Urgency: Normal
• Issue & fix info: Newcomer
• Bug behavior facts: Embedded/Client difference
• Assignee: Dag H. Wanvik
• Reporter: Will Gomes
• Created: 05/Aug/09 14:10
• Updated: 08/Feb/11 10:44
• Resolved: 31/Aug/09 22:21

Description

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.

Issue Links

• is duplicated by: DERBY-3626 Issue with bracketed SQL comments on a remote database connection from ij
• is related to: DERBY-5011 [patch] Client driver lexer to determine statement type: fix bad attempt at incrementing a variable