jdbcDriverOOo logo Historical

Ce document en français.

Regarding installation, configuration and use, please consult the documentation.

What has been done for version 0.0.1:

What has been done for version 0.0.2:

What has been done for version 0.0.3:

What has been done for version 0.0.4:

What has been done for version 1.0.0:

What has been done for version 1.0.1:

What has been done for version 1.0.2:

What has been done for version 1.0.3:

What has been done for version 1.0.4:

What has been done for version 1.0.5:

What has been done for version 1.0.6:

What has been done for version 1.0.7:

What has been done for version 1.0.8:

What has been done for version 1.1.0:

What has been done for version 1.1.1:

What has been done for version 1.1.2:

What has been done for version 1.1.3:

What has been done for version 1.1.4:

What has been done for version 1.1.5:

What has been done for version 1.1.6:

What has been done for version 1.2.0:

What has been done for version 1.2.1:

What has been done for version 1.2.2:

What has been done for version 1.2.3:

What has been done for version 1.2.4:

What has been done for version 1.3.0:

Normally, I managed to cover the entire scope of the UNO API (com.sun.star.sdbc, sdbcx and sdb), which took quite a while, but I didn’t initially think I would get there.

What has been done for version 1.3.1:

What has been done for version 1.3.2:

The UNO SDBCX API can now be used for creating databases, as is the case for the latest versions of extensions using jdbcDriverOOo. It is possible to create tables, using the UNO API, with the following characteristics:

Using the UNO API to create databases will allow you to use code that is independent of the underlying database.

Clients using the jdbcDriverOOo driver can access features of the underlying JDBC driver through the XDriver.getPropertyInfo() method in order to access the necessary parameter when creating tables and display privileges correctly. These parameters being accessible directly by the driver can be obtained before any connection and therefore allows the creation of the database during the first connection.

What has been done for version 1.3.3:

What has been done for version 1.4.0:

What has been done for version 1.4.1:

What has been done for version 1.4.2:

What has been done for version 1.4.3:

What has been done for version 1.4.4:

What has been done for version 1.4.5:

What has been done for version 1.4.6:

What has been done for version 1.5.0:

What remains to be done for version 1.5.0: