Why are you giving up? I still believe there is a possible solution to this, so that the Derby community can ship with JDBC4 capability - to that end, I'm doing what I can to try to find a solution with Sun on this.
Do people not care? I just don't understand. Derby can be the world's first database with JDBC4 support, so it's there and ready when Mustang is released. This means that Sun has to fork Derby, and also JavaDB is therefore more technically advanced than Derby, and no one wants that either. No one wins here. Lets find a solution. I don't think it will take much longer. geir Jean T. Anderson wrote: > I'm looking for wording we can plug into both the release notes and > strategic pages in the documentation. How does this sound? > > > This documentation references new JDBC 4.0 functionality that is not > enabled in this Apache Derby 10.2 release. Until a final Java SE 6 > release is available, JDBC 3.0 will be available by default when used > with a Java SE 6 beta build. JDBC 4.0 functionality will only be > available to developers who download Java SE 6 themselves and build > Derby with it. > > tweaks? comments? corrections? > > thanks, > > -jean > >
