office-gobmx/connectivity/registry
Lionel Elie Mamane 9b6906bbf3 tdf#120713 correctly handle boolean values in filters
This commit has two parts:
 - Hardcode the correct BooleanComparisonMode in the firebird-sdbc driver
   (this fixes on Firebird databases, among others, the AutoFilter for bools)
 - Generic to all DBMS, have the "form-based filter" obey the BooleanComparisonMode

Change-Id: Ib14e6c3d5cb773ae1f972840f8b53062f0224396
Reviewed-on: https://gerrit.libreoffice.org/62319
Tested-by: Jenkins
Reviewed-by: Lionel Elie Mamane <lionel@mamane.lu>
2018-10-25 10:03:13 +02:00
..
ado/org/openoffice/Office/DataAccess Fix some drivers xcu (connectivity/registry) 2018-10-03 07:03:13 +02:00
calc/org/openoffice/Office/DataAccess
dbase/org/openoffice/Office/DataAccess
evoab2/org/openoffice/Office/DataAccess
firebird/org/openoffice/Office/DataAccess tdf#120713 correctly handle boolean values in filters 2018-10-25 10:03:13 +02:00
flat/org/openoffice/Office/DataAccess
hsqldb/org/openoffice/Office/DataAccess
jdbc/org/openoffice/Office/DataAccess Fix some drivers xcu (connectivity/registry) 2018-10-03 07:03:13 +02:00
macab/org/openoffice/Office/DataAccess
mork/org/openoffice/Office/DataAccess
mysql_jdbc/org/openoffice/Office/DataAccess Revert removal of mysql jdbc connector 2018-10-14 22:16:05 +02:00
mysqlc/org/openoffice/Office/DataAccess Fix some drivers xcu (connectivity/registry) 2018-10-03 07:03:13 +02:00
odbc/org/openoffice/Office/DataAccess Fix some drivers xcu (connectivity/registry) 2018-10-03 07:03:13 +02:00
postgresql/org/openoffice/Office/DataAccess
writer/org/openoffice/Office/DataAccess
README

xcu files are made from several sections, the main ones are: Properties and Features

Property: actual setting with its underlying type and its default value

Feature: a boolean that says "let the user change that setting in the Advanced Settings UI"

This is checked by using officecfg/registry/schema/org/openoffice/Office/DataAccess/Drivers.xcs
and configmgr mechanism
There are two kinds of properties named "Value":
- first one is in "Property" groups and has a static oor:type="any" (can take on boolean, int and other types of values)
- second one is in "Feature" groups and has a static oor:type="boolean" so can take on only boolean values.

Each node in Feature section must have an equivalent in Property section
Most of the time the node name of both sections should be equal,
however there are 4 known exceptions (more?):
- "UseBracketedOuterJoinSyntax" feature => "EnableOuterJoinEscape" property
- "UseDOSLineEnds" feature => "PreferDosLikeLineEnds" property
- "UseSQL92NamingConstraints" feature => "EnableSQL92Check" property
- "UseKeywordAsBeforeAlias" feature => "GenerateASBeforeCorrelationName"

See dbaccess/source/ui/dlg/DbAdminImpl.cxx, ODbDataSourceAdministrationHelper constructor, eg:
m_aIndirectPropTranslator.emplace( <ID>, <property> )
and dbaccess/source/ui/misc/dsmeta.cxx, lcl_getFeatureMappings() function, eg:
{ <ID>, <feature> }