No software connecting to an LDAP database through JDBC can be expected
to know anything at all about LDAP, so no such software can be expected
to be able to decode the RFC 4517 Postal Address format.

Fredrik Roubert authored May 01, 2022 and Howard Chu committed May 02, 2022

LibreOffice Base expects to be able to call LdapResultSet.getLong() on
an empty Types.INTEGER field without any exception being thrown and the
exception that Long.parseLong() throws when passed an empty string will
terminate the query with an error message.

Fredrik Roubert authored May 01, 2022 and Howard Chu committed May 02, 2022

Using TLS is becoming increasingly more common and the LDAP library has
support for this since a long time already, the JDBC connection string
just needs to support a new property to allow this to be configured.

Fredrik Roubert authored May 01, 2022 and Howard Chu committed May 02, 2022

No software connecting to an LDAP database through JDBC can be expected
to know anything at all about LDAP, so no such software can be expected
to be able to do anything useful with an LDAP alias entry. LDAP aliases
must therefore always be dereferenced in the JDBC driver.

This must have been the original intent behind this code, that Base64
encoding should be used for data that isn't plain Unicode text and it
should have been calling isValidUTF8() to check for this all along.

* Added SPML and DSMLv2 support in the browser
* Added support JDBC connections in the browser
* Added export to CVS support in the browser
* If the JLDAP binary used doesn't support SPML or JLDAP, the browser won't support
* Fixed a bug with ignoring commit/rollback ITS 3600

* Added support for RootDSE in the SQL Directory Browser
* Setting the maximum number of entries to 0 results in no limit
* Single quotes are now recognized in INSERT/UPDATE/UPDATE ENTRY

* Supports DSMLv2
* Better operational performance on searches
* Created a browser which may be used to browse directories using SQL

Added ability for  jdbc bridge to perform  ldap modify commands using the statement:
UPDATE ENTRY dn DO operation SET attribute=value WHERE condition
operation may be ADD REPLACE or DELETE
Added a IGNORE_TRANSACTION flag to the initialization parameters that allows transaction calls to be ignored

Fixed issue with with SELECT statements that retrieve only a DN.  If only a DN is in the field list, then the drivers will send "1.1" as the only attribute requested as opposed to an emptry list.

fixed dn and comma issues with SELECT, UPDATE and DELETE
by adding EXP_ROWS=true in the connection string, row expansion can be used for retrieving results in addition to column expansion and concatination