db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: Disussion surrounding holding off metadata changes until certain issues resolved
Date Mon, 24 Apr 2006 16:20:46 GMT
Dag H. Wanvik wrote:

>K
>
>
>However, for the four other metadata calls that have changed with SUR:
>
>	 deletesAreDetected(TYPE_SCROLL_INSENSITIVE) -> true
>	 updatedAreDetected(TYPE_SCROLL_INSENSITIVE) -> true
>	 ownDeletesAreVisible(TYPE_SCROLL_INSENSITIVE) -> true
>	 ownUpdatesAreVisible(TYPE_SCROLL_INSENSITIVE) -> true
>
>we are not so lucky. On trying this for 10.2 trunk I see that JCC
>returns true for these as well (both in soft upgrade and and after
>hard upgrade, thanks to DERBY-1176), which *is* a regression for JCC
>apps:
>
>  
>
This is a regression for JCC, but is not a problem for the original
client release with the 10.2 server?  I don't understand why JCC and the
original client 10.1.1.0 release would behave differently in this
regard. Could you explain?

Thanks

Kathey






Mime
View raw message