Difference between revisions of "Database/Drivers/MySQL Native/Architecture"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 1: Line 1:
The below picture illustrates the current architecture for the existing MySQL driver. Note especially the bridges (from JDBC resp. ODBC to SDBC), which make the architecture overly complex due to additional translation overhead.
+
__TOC__
 +
=== Wrapped Access ===
 +
The below picture illustrates the current architecture for the existing MySQL driver, where a generic driver (JDBC/ODBC) is wrapped
 
[[image:Mysql_driver_architecture_old.png|center|frame|MySQL Driver architecture - present]]
 
[[image:Mysql_driver_architecture_old.png|center|frame|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 ([http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/module-ix.html SDB]).
  
 +
=== Direct Access ===
 +
The below picture illustrates the new architecture, where a dedicated C++ driver (Connector/OOo) talks to the MySQL server using either the MySQL client library or the Connector/C++
 
[[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''''
 +
* the Connector/C++ does not exist yet
 +
* Currently, the MySQL Client Library is linked to / shipped with the MySQL native driver, thus effectively part of OpenOffice.org.
 +
* Whether the Connector/C++ will be part of the MySQL native driver (and thus be part of an OpenOffice.org installation) needs to be clarified

Revision as of 09:54, 6 May 2008

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 either the MySQL client library or the Connector/C++

MySQL Driver architecture - future

'Notes'

  • the Connector/C++ does not exist yet
  • Currently, the MySQL Client Library is linked to / shipped with the MySQL native driver, thus effectively part of OpenOffice.org.
  • Whether the Connector/C++ will be part of the MySQL native driver (and thus be part of an OpenOffice.org installation) needs to be clarified
Personal tools