Great. I have to say your part about how this "will translate into SQL
and JDBC compatibility with the masking issues going on" has me a bit
stumped -- can you explain in some more detail?
Thanks,
David
Kathey Marsden wrote:
David W. Van Couvering wrote:
So, how about
"Older versions of Derby jars will get their expected behavior in a
mixed version environment regardless of jar ordering. Newer versions
of Derby jars will get new behavior if the newer jar files are loaded
first, and older behavior if the older jar files are loaded first.
I like the sound of it! Now that I know for sure that is what we are
promising users, next week I'll try some stuff out with the patch and
try to understand how maintaining the internal API backward/forward
compatibility will translate into SQL and JDBC compatibility with the
masking issues going on.
Kathey
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
