Rick Hillegas wrote:
Thanks, Kristian. This is a good suggestion. I have to admit, though,
that I can't seem to figure out how to mark the issue invalid--maybe I
should drink some more coffee. I have reopened it and the only
Workflow options I see are "Resolve", "Close", and "Start Progress".
What's the magic?
Click "Resolve" (or "Close"), then choose "Invalid" instead of "Fixed".
If you click the question mark next to the pull down menu, you can also
see what the Jira people (?) mean with the different resolution types.
regards,
--
Kristian
Thanks,
-Rick
Kristian Waagan (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649629#action_12649629
]
Kristian Waagan commented on DERBY-3957:
----------------------------------------
Not really important at all, except for the quality of the Jira issue
reports, but shouldn't this issue be resolved as "Invalid" due to the
operator error?
Fixed - A fix for this issue is checked into the tree and tested.
Invalid - The problem isn't valid and it can't be fixed.
Generated columns are not recalculated when you update a column
through an updatable ResultSet.
-----------------------------------------------------------------------------------------------
Key: DERBY-3957
URL: https://issues.apache.org/jira/browse/DERBY-3957
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.5.0.0
Reporter: Rick Hillegas
Assignee: Rick Hillegas
ResultSet.updateXXX() does not update a generated column when you
update one of the columns it depends on.
