Hi Ariel, > In *all* cases > > * you need something provided by MySQL (the ODBC driver or the JDBC driver) > * from OOo's side, it will "comunicate" through 3 different drivers for > the three different cases 1, 2 y 3 (3 being a dedicated driver for MySQL). > ... > and reading only a few, I could get that > org.openoffice.comp.drivers.MySQL.Driver works like a "delegator" > (connectivity/source/drivers/mysql/YDriver.cxx - ODriverDelegator), that > is, it accepts both ODBC and JDBC connection to MySQL: > ... > At least that's what I understood as "delegator" reading this few lines > of code (Frank will correct me, sure ;-) ). > > But what is that this dedicated driver adds? what is the advantage of > choosing 3.1 instead of 1, and 3.2 instead of 2?
Your understanding is right, the MySQL driver only wraps a JDBC or ODBC driver, and cares for a few of MySQL ... unique features, by kind of "normalizing" them. Also, it adds a few features, like API for user administration. > Some side thoughts: > * first time I see the XUnoTunel in action (ODriverDelegator::connect) Uhoh. XUnoTunnel is something to avoid, if possible. It does what the name tells: It tunnels UNO, which is a Bad Thing (TM), conceptually. I am not too happy with it being used there (or anywhere else). Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
