I am trying to avoid an explosion of cases because I think that will
cause a lot of support headaches. The simplification I was hoping for
was one set of behaviors governing clients/servers operating at the
current Derby and JDBC rev level and another set of behaviors for all
other combinations.
I would have no issue if existing JCC/10.1 network clients continued to
report BOOLEAN as SMALLINT, as they seem to. I would have an issue if
you changed the current correct behaviour of embedded under jdk 1.3 to
match that.
I will abandon my attempt to simplify the support problem. Instead, I
will amend the spec as follows: I will add a matrix describing how the
BOOLEAN datatype will appear to clients based on client and server rev
and vm.
