Difference between revisions of "Database/Drivers/MySQL Native/Architecture"
From Apache OpenOffice Wiki
		< Database | Drivers | MySQL Native
		
		
| Line 12: | Line 12: | ||
''''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.  | ||
| + | |||
| + | |||
| + | [[Category:Database Drivers]]  | ||
Latest revision as of 01:03, 23 November 2009
Wrapped Access
The below picture illustrates the current architecture for the existing MySQL driver, where a generic driver (JDBC/ODBC) is wrapped
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)
'Notes'
- Currently, the MySQL Client Library is linked to / shipped with the MySQL native driver, thus effectively part of OpenOffice.org.
 

