On 12/18/14 5:54 PM, Bryan Pendleton wrote:
What level of client/server compatibility is Derby meant to
support. This is just about the derby version of the software
on the client machine and the version of the software on the
server machine.
I'm not sure I've seen much written about this, either, and
I agree it would be valuable to document.
There is
http://db.apache.org/derby/papers/versionupgrade.html
but that's all about the engine proper, not about the client-server
protocol, which is what I think you're most interested in.
This is quite old and doesn't say much at all:
http://db.apache.org/derby/papers/DerbyClientSpec.html#-N10306
bryan
I also can't find any statement about what users should expect. It seems
that the network client was introduced without any statement about the
compatibility rules.
It does not appear to me that we have run the compatibility tests for a
long time. For 10.11.1, Knut ran suites.all against a soft-upgraded
database, but that's not the compatibility testing which Kathey used to
run: http://wiki.apache.org/db-derby/TenElevenOneChecklist. Even less
was done for 10.10.1:
http://wiki.apache.org/db-derby/TenTenOneChecklist. Ingemar did some
compatibility testing for 10.9.1, but I don't know if it was the full
battery which Kathey used to run:
http://wiki.apache.org/db-derby/TenNineOnePlatformTesting.
If we state compatibility rules, then we should make sure that we can
verify those claims when we vet releases.
Thanks,
-Rick
