These changes were put back a while ago and rick made an integration
for this into the derby codeline.
There will be one more change to Types.java i believe in order to
prevent a collision for a large number of users of a specific database
due to their own types colliding with the JDBC
Hi David,
With build 95 of the 1.6 beta, various constants in DatabaseMetaData
changed name (see DERBY-1530). The constants named functionParameter*
changed name to functionColumn*. From this build output, it appears that
you have not synced up to the state of the mainline after DERBY-1530
I am running with the latest drop from the jdk 1.6 site, and I have the
latest stuff from the trunk, and I am getting the following errors.
These appear to be members of java.sql.DatabaseMetaData. I am hoping
someone familiar with this area of the code can provide some quick
guidance...
I just double-checked, and in ~/ant.properties I have
jdk16=/usr/jdk/jdk1.6.0
and then:
bash-3.00$ /usr/jdk/jdk1.6.0/bin/java -version
java version 1.6.0-rc
Java(TM) SE Runtime Environment (build 1.6.0-rc-b96)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b96, mixed mode, sharing)
Which is the
Hi David,
There were changes in this area to the DatabaseMetaData and it looks
like this test might not have caught up to it.
-lance
David Van Couvering wrote:
I am running with the latest drop from the jdk 1.6 site, and I have
the latest stuff from the trunk, and I am getting the following
H, so Rick wrote on 8/11:
Build 95 should be the last Mustang version which changes JDBC signatures.
David wrote: (today)
Java(TM) SE Runtime Environment (build 1.6.0-rc-b96)
Lance wrote: (today)
There were changes in this area to the DatabaseMetaData and it looks
like this test
Well, that doesn't fully make sense, since nobody else seems to be
complaining about this. Wouldn't we get build failures in the
regression nightlies and other JDBC4 developers if this were a global
issue? I've had this problem for two days now...
David
Lance J. Andersen wrote:
Hi David,
David Van Couvering [EMAIL PROTECTED] writes:
Well, that doesn't fully make sense, since nobody else seems to be
complaining about this. Wouldn't we get build failures in the
regression nightlies and other JDBC4 developers if this were a global
issue? I've had this problem for two days
