harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Zhang" <zhanghuang...@gmail.com>
Subject Re: [classlib][sql] Non-bug difference of SerialClob.setString(long, String)?
Date Thu, 08 Mar 2007 01:56:19 GMT
If no one objects, I'll file a JIRA issue to record it as non bug difference
from RI.

On 3/7/07, Andrew Zhang <zhanghuangzhu@gmail.com> wrote:
>
> Hi guys,
>
> As spec says, SerialClob.setString(long, String) throws SerialException -
> if there is an error accessing the CLOB value; if an invalid position is
> set; if an invalid offset value is set; if number of bytes to be written is
> greater than the SerialClob length; or the combined values of the length and
> offset is greater than the Clob buffer. But following code throws
> ArrayIndexOutOfBoundException instead.
> public void test() {
>         String s = "hello";
>         char[] buf = s.toCharArray();
>         SerialClob serialClob = new SerialClob(buf);
>         try {
>             serialClob.setString(2, "hello");
>             fail("should throw SerialException");
>         } catch (SerialException e) {
>             // expected
>         }
> }
>
> Shall we follow RI or spec for this case?
> We encounter many similar non-bug differences in SerialBlob, and IMHO,
> we'd better follow spec and not copy RI's bug.
> What's your opnion? Thanks!
>
> --
> Best regards,
> Andrew Zhang
>



-- 
Best regards,
Andrew Zhang

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message