db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta Satoor" <msat...@gmail.com>
Subject Re: Question about next() and previous() on CollationElementIterator.
Date Mon, 17 Sep 2007 20:13:29 GMT
Thanks for the info on bug, Knut and thanks to the person who entered the
bug. I updated that bug with brief info on what I found with further
testing.

Mamta


On 9/17/07, Knut Anders Hatlen <Knut.Hatlen@sun.com> wrote:
>
> Mamta Satoor <msatoor@gmail.com> writes:
>
> > I did a little more testing with next() and previous() on
> > CollationElementIterator with Sun's jdk 14 and IBM's jdk 14.
> >
> > It appears that the problem happens with Sun's jdk when a character has
> more
> > than one collation element associated with it.
> >
> > For instance, when I get CollationElementIterator for "a"(it has only
> one
> > collation element associated with it) and do next() and previous() on
> it, it
> > behaves as expected which is next() and previous() both return the same
> > collation element  both with Sun's jdk14 and IBM's jdk14.
> >
> > But when I get CollationElementIterator for "\uFA2D"(it has 2 collation
> > elements associated with it) and do next() and previous() on it, it does
> not
> > behave correctly under Sun's jdk14. It appears that Sun's jdk treats the
> > previous() as next() when there is more than one collation element
> > associated with a character. IBM's jdk14 returns the same collation
> element
> > for next() and previous() on CollationElementIterator for "\uFA2D"
> >
> > Is there a way to followup this problem with Sun's JDK group?
>
> Hi Mamta,
>
> Seems like they've already been made aware of this thread. Please see
> http://bugs.sun.com/view_bug.do?bug_id=6603190. Thanks for investigating
> the issue!
>
> --
> Knut Anders
>

Mime
View raw message