db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geir Magnusson Jr <g...@pobox.com>
Subject Re: catch-22: Derby, Mustang, and JCP issue
Date Fri, 23 Jun 2006 03:19:55 GMT

Brian McCallister wrote:
> On Jun 22, 2006, at 7:09 PM, Daniel John Debrunner wrote:
>> "You cannot have a GA version of a JDBC 4 driver until JSR 221 goes
>> final."
>> Where does this restriction come from?
> Until a spec is final I don't see how you can have a certified compliant
> implementation of that spec. It might be as easy as not claiming JDBC 4.0
> compliance until *after* JSR-221 is final, than saying, "huh, gee whiz,
> we pass the TCK!"

The only problem I see is that by the letter of the law, there is no
right to implement and distribute JDBC4's public draft.

I guess the first thing to figure out is what from the JDBC4 expert
group has actually been implemented.

> If the interfaces happen to exist in a release before the spec is final,
> well, cool.

Sun used to have some strange arguments about spec API copyrights which
made that uncool unless you passed the TCK (which implied completion of
the JSR....)

> Folks using them are at risk of the spec changing at the last
> minute, so I would put bright red warnings around them if they are event
> documented before the official release of the spec (not of Derby).

Or just leave JDBC4 out of the GA release, and given it's only a
database driver, just offer it as a second jar when it's possible to do so.

Why tie the DB release cycle to an updated driver?  Won't a JDBC3 driver
work well too?


View raw message