| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Greetings, |
| 5 |
|
| 6 |
Since incorporating more JDBC support into the tree, I have gotten a few |
| 7 |
inquiries on how we plan to support different driver types. This email |
| 8 |
will hopefully explain the direction I intend to guide the process |
| 9 |
towards, so that Java developers listening can have an opportunity to |
| 10 |
voice any concerns. |
| 11 |
|
| 12 |
[ BACKGROUND ] |
| 13 |
|
| 14 |
JDBC Types: |
| 15 |
|
| 16 |
Type 1: JDBC-ODBC bridge, plus an ODBC driver |
| 17 |
(for things like dBase, Access, Excel) |
| 18 |
Type 2: native API, part-Java driver |
| 19 |
(rarely used) |
| 20 |
Type 3: 100% Java driver for database middleware |
| 21 |
Type 4: 100% Java driver for direct connections |
| 22 |
|
| 23 |
JDBC Versions: JDBC 2.0 vs 3.0? |
| 24 |
|
| 25 |
I won't attempt to explain this detail. JDBC 3.0 is for Java 1.4 and |
| 26 |
later only, and has improvements in pooling, and integration with J2EE. |
| 27 |
It should be noted that the lead author of JDBC 3.0 (Jon Ellis) is also a |
| 28 |
Gentoo developer. :) |
| 29 |
|
| 30 |
|
| 31 |
[ IMPLEMENTATION DETAILS ] |
| 32 |
|
| 33 |
1. Type 4 drivers will be the default for any data source that has Type 4 |
| 34 |
drivers available. |
| 35 |
|
| 36 |
2. Type 1 drivers will be added only when Type 4 drivers are not available |
| 37 |
(as will normally be the case). |
| 38 |
|
| 39 |
3. I am not expecting to see any support for Type 2 drivers in the tree. |
| 40 |
If they do exist, they will be done as separate packages from any other |
| 41 |
driver type, because of portability issues. |
| 42 |
|
| 43 |
4. Type 3 drivers are expected to be included if they are available, in |
| 44 |
the same ebuilds that install the Type 4 drivers. This will mean the |
| 45 |
addition of one local USE flag: "jdbc-type3". |
| 46 |
|
| 47 |
5. Setting "jdbc-type3" will ensure that Type 3 drivers will get installed |
| 48 |
(if they exist) instead of Type 4 drivers. Both cannot be installed at |
| 49 |
the same time, as both drivers would end up in package.env's CLASSPATH -- |
| 50 |
which is not a sane configuration. |
| 51 |
|
| 52 |
6. JDBC 2.0 drivers will be kept in separate packages from JDBC 3.0 |
| 53 |
drivers. |
| 54 |
|
| 55 |
Questions? Comments? |
| 56 |
|
| 57 |
Cheers, |
| 58 |
Dylan Carlson |
| 59 |
|
| 60 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F |
| 61 |
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F |
| 62 |
-----BEGIN PGP SIGNATURE----- |
| 63 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 64 |
|
| 65 |
iD8DBQE+xGaTPQS8wXCOFl8RAgg3AJ45GoLyvEaUFPnlzUuQcJ1dfnoo9gCbBEvI |
| 66 |
DRBsk0+dDjpsMJbbMgneMZU= |
| 67 |
=p4G8 |
| 68 |
-----END PGP SIGNATURE----- |
| 69 |
|
| 70 |
|
| 71 |
-- |
| 72 |
gentoo-dev@g.o mailing list |
Archives