db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3705) In Net Client mode, negative values for stream length are accepted without an exception for PreparedStatement.setAsciiStream()
Date Tue, 03 Jun 2008 19:54:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-3705:
-----------------------------------

             Priority: Minor  (was: Critical)
    Affects Version/s: 10.5.0.0

Good catch Suran :)
Nice work on converting the big test.

I''m changing the priority from critical to minor (press the yellow question mark next to
the priority field to see descriptions of the various levels). There is a simple workaround
available; don't specify negative stream lengths.
It would be interesting to know what happens if you do specify a negative length though, and
if that causes data corruption the priority would have to be raised again.

I'll happily review your patch tomorrow.

> In Net Client mode, negative values for stream length are accepted without an exception
for PreparedStatement.setAsciiStream()
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3705
>                 URL: https://issues.apache.org/jira/browse/DERBY-3705
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.4.1.3, 10.5.0.0
>         Environment: Windows XP SP2, Derby trunk SVN checkout
>            Reporter: Suran Jayathilaka
>            Assignee: Suran Jayathilaka
>            Priority: Minor
>         Attachments: derby-3705.diff
>
>
> This is related to Cloudscape bug 4250.
> Pass negative length as the stream length for various setXXXStream methods should throw
an exception. But in Net Client mode, passing a negative value as stream length to PreparedStatement.setAsciiStream()
doesn't throw an exception.
> e.g. //from store/StreamingColumn
> PreparedStatement ps = prepareStatement("insert into "
> 				+ "testLongVarCharInvalidStreamLength11 values(?, ?, ?)");
> 		ps.setInt(1, 100);
> 		try {
> 			println("===> testing using setAsciiStream with -2 as length");
> 			ps.setAsciiStream(2, fileIn, -2); // should throw exception here but doesn't.
>                  }
> This issue has been fixed for embedded mode, but not for client mode.

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


Mime
View raw message