[
https://issues.apache.org/jira/browse/DERBY-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564932#action_12564932
]
Stan Bradbury commented on DERBY-448:
-------------------------------------
I think I understand a little better now about this issue and why IJ should
display warnings - I assume that syntax errors are Warnings and it would be a
pain not get get those.
My real problem is with how IJ handles multiple Warning generated by the same
statement. This is not shown by this JIRA issue but, I now believe, is what I
observed when working with DERBY-3219. With a smaller set of data than
provided with the DERBY-3219 reproduction the query did not fail but returned
data and the following warning for each of the ~1000 records:
WARNING 01003: Null values were eliminated from the argument of a column
function.
I would find it helpful to display a warning only once and not to iterate over
the entire stack of duplicate Warnings. Does this seem like a reasonable
statement for an enhancement request?
> delete on an empty table generates warning
> ------------------------------------------
>
> Key: DERBY-448
> URL: https://issues.apache.org/jira/browse/DERBY-448
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.0.2.1
> Environment: Solaris
> Reporter: simmi iyer
>
> 1. Launch ij to connect to Derby using embedded driver.
> 2. Issue delete command at ij prompt
> ij>delete from table ;
> 3. This generates a warning
> 0 rows inserted/updated/deleted
> WARNING 02000: No row was found for FETCH, UPDATE or DELETE; or the result of
> a query is an empty table.
> There are two issues here:
> 1. It should say 0 rows deleted instead of 0 rows inserted/deleted/updated.
> 2. WARNING should not be shown.
> thx
> Simmi.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
