Difference between revisions of "Database/Drivers/MySQL Native/Architecture"
From Apache OpenOffice Wiki
< Database | Drivers | MySQL Native
(→Direct Access) |
|||
| Line 8: | Line 8: | ||
=== Direct Access === | === Direct Access === | ||
| − | The below picture illustrates the new architecture, where a dedicated C++ driver (Connector/OOo) talks to the MySQL server using | + | The below picture illustrates the new architecture, where a dedicated C++ driver (Connector/OOo) talks to the MySQL server using the MySQL client library (libmysql) |
[[image:Mysql_driver_architecture_new.png|center|frame|MySQL Driver architecture - future]] | [[image:Mysql_driver_architecture_new.png|center|frame|MySQL Driver architecture - future]] | ||
''''Notes'''' | ''''Notes'''' | ||
| − | |||
* Currently, the MySQL Client Library is linked to / shipped with the MySQL native driver, thus effectively part of OpenOffice.org. | * Currently, the MySQL Client Library is linked to / shipped with the MySQL native driver, thus effectively part of OpenOffice.org. | ||
| − | |||
Revision as of 07:15, 7 May 2008
Contents
Wrapped Access
The below picture illustrates the current architecture for the existing MySQL driver, where a generic driver (JDBC/ODBC) is wrapped
MySQL Driver architecture - present
Notes
- Note the additional layer consisting of the JDBC/ODBC->SDBC bridge, which introduces additional complexity, and loss of information (as every abstraction layer)
- The picture is not strictly correct. The applications usually do not work directly on the SDBCX layer, but instead on a layer providing yet more convenience (SDB).
Direct Access
The below picture illustrates the new architecture, where a dedicated C++ driver (Connector/OOo) talks to the MySQL server using the MySQL client library (libmysql)
MySQL Driver architecture - future
'Notes'
- Currently, the MySQL Client Library is linked to / shipped with the MySQL native driver, thus effectively part of OpenOffice.org.
