Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <359715321.1240779330394.JavaMail.jira@brutus>
Date: Sun, 26 Apr 2009 13:55:30 -0700 (PDT)
From: "Tiago R. Espinha (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4099) Update Multiple Columns SQL
In-Reply-To: <2133212083.1237286210621.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-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702935#action_12702935 ] 

Tiago R. Espinha commented on DERBY-4099:
-----------------------------------------

Given this, then the bug would be on MySQL's end and not on ours. On a strictly personal level, I do prefer the behaviour specified by the standard.

> Update Multiple Columns SQL
> ---------------------------
>
>                 Key: DERBY-4099
>                 URL: https://issues.apache.org/jira/browse/DERBY-4099
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Meenakshi Sundar Sitaraman
>            Priority: Critical
>
> When I try to execute the following query
> update table_name set n1=5, average=(n1+n2)/2 where ....
> The new value of n1 (viz. 5 in this case) is not used when calculating the average. While the new value of n1 is used in MySQL, the old value is used in Derby.
> Appreciate your support in resolving this issue.

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