db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: [jira] Resolved: (DERBY-2358) Exception during multi-row update if a value to be set is a parameter and is set using a streaming inteface, such as setBinaryStream.
Date Tue, 20 Feb 2007 14:42:45 GMT
Daniel John Debrunner (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/DERBY-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
> 
> Daniel John Debrunner resolved DERBY-2358.
> ------------------------------------------
> 
>     Resolution: Duplicate
> 
> Duplicate of DERBY-2111

Just a general question:
When we get duplicates, like this, is it okay to close it at once, or 
should it follow the state of the duplicate issue?


I'm an advocate of closing Jira issues when they can be closed, that's 
why I ask :)



-- 
Kristian

> 
>> Exception during multi-row update if a value to be set is a parameter and is set
using a streaming inteface, such as setBinaryStream.
>> -------------------------------------------------------------------------------------------------------------------------------------
>>
>>                 Key: DERBY-2358
>>                 URL: https://issues.apache.org/jira/browse/DERBY-2358
>>             Project: Derby
>>          Issue Type: Bug
>>          Components: JDBC, SQL
>>    Affects Versions: 10.3.0.0
>>            Reporter: Daniel John Debrunner
>>            Priority: Minor
>>
>> A statement like
>> UPDATE T_MAIN SET V=?
>> will fail if V is set for more than one row and the parameter is set using setAsciiStream,
setBinaryStream or setCharacterStream.
>> Most likely because the stream is read twice.
>> See code in TriggerTest commented with this bug number.
> 


Mime
View raw message