Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1543002641.1251309359308.JavaMail.jira@brutus>
Date: Wed, 26 Aug 2009 10:55:59 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4338) Network client raises error
 "executeQuery method can not be used for update" when sql is preceded by /*
 */ comments
In-Reply-To: <2088486472.1249481475148.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748052#action_12748052 ] 

Dag H. Wanvik commented on DERBY-4338:
--------------------------------------

> /* asdfads */ { call syscs_util.syscs_checkpoint_database() }; 

Yes, I realize that I could have chosen to remove the left brace here easily, but the old code didn't handle that case after an end-of-line comment so I was hesitant to change behavior. But thinking again
I agree it's better to be consistent. I don't think it should cause much a problem: the only change would be to correctly classify an escaped call as such after a end-of-line comment.

As for the comment stubs, I moved the comments up to the delim variable. I'll remove the stubs
and provide a method comment as well.

> 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
>          Components: Network Client
>    Affects Versions: 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0
>            Reporter: Will Gomes
>            Assignee: Dag H. Wanvik
>             Fix For: 10.6.0.0
>
>         Attachments: derby-4338-a.diff, derby-4338-a.stat, derby-4338-b.diff, derby-4338-b.stat
>
>
> 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.