On Sat, 2005-12-17 at 22:08 +0100, Roman Rokytskyy wrote:

> > I think this aspect is holding up the ebuilds. Not really sure what's
> > holding them up. I have yet to post a jdbc2 till I get the ebuild
> > squared away for jdbc3. Since 2 is just like 3 but with native stuff.
>
> Sorry, it might be that we have misunderstanding here...

Possibly

> jdbc2 is "JDBC 2.0"
> or "jdbc type 2" driver?

Correct, with native libaries, ie libjaybird2.so

> if latter, then you have to rename jdbc3 into
> jdbc4,

Ok, so JDBC type 4 driver, is pure Java.

> since "jdbc type 3" driver is the one that has a server-side
> component that uses JNI to talk to the database server, but has its own wire
> protocol to talk to the client-side jars.

So InterClient was JDBC 3? I thought it was 2. Now I am confused? :)

Which type does libjaybird2.so belong to?

--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com