Type: info
Title: new: css.sdb.BooleanComparisonMode
Posted by: [EMAIL PROTECTED]
Affected: [EMAIL PROTECTED],-
Effective from: CWS dba24c
*Summary*
--------
+ ::com::sun::star::sdb::BooleanComparisonMode
*Description*
-------------
There is (and has been for a long time) a setting at a data source
(css.sdb.DataSource.Settings) which controls how Base's SQL
parser/generator should express boolean comparison predicates, when
generating SQL statements to be sent to the database backend. (such a
setting is necessary since there exists no standard SQL way to check
for boolean values.)
The different modes supported here are now explicitly available at the
css.sdb.BooleanComparisonMode constants group:
/** specifies different modi how boolean comparison predicates are to be
generated by a <type>SingleSelectQueryComposer</type>.
*/
constants BooleanComparisonMode
{
/** denotes the default comparison
<p>Most databases support comparing boolean expressions or
column values directly with integer values:
<code><em>column</em> = 0</code> respectively
<code><em>column</em> = 1</code>.</p>
*/
const long EQUAL_INTEGER = 0;
/** requires to use <code>IS <em>boolean_literal</em></code> for
boolean comparison.
<p>That is, the generated comparison predicates will be
<code><em>column</em> IS TRUE</code> resp.
<code><em>column</em> IS FALSE</code>.</p>
*/
const long IS_LITERAL = 1;
/** requires to use <code>= <em>boolean_literal</em></code> for
boolean comparison.
<p>That is, the generated comparison predicates will be
<code><em>column</em> = TRUE</code> resp.
<code><em>column</em> = FALSE</code>.</p>
*/
const long EQUAL_LITERAL = 2;
/** requires to use an Microsoft Access compatible syntax for boolean
comparison.
*/
const long ACCESS_COMPAT = 3;
};
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]