Skip to main content

2025.2 to 2026.0

Wildcards in search strings are treated as normal characters​

What changed​

Starting with ADITO 2026.0, wildcards in search strings will be escaped. Partially matching searches must now make use of the appropriate search operators like CONTAINS, CONTAINS_NOT, STARTS_WITH, END_WITH and the respective search term. The change affects content search as well as search filters.

Why it matters​

This change makes it possible to search for the characters '%', '_', '*', '?' and '\'. It also fixes issues with some constellations of partially matching operators

If saved filters use wildcards in their search strings, they should be updated accordingly.

For example, replace:

// search for "test" and "greatest", old  
CONTAINS *test

with

// search for "test" and "greatest", new
ENDS WITH test

If necessary, it is also possible to create a custom filterExtension as a workaround.

Developer comments on why this was changed​

In previous versions of ADITO, the behavior of the wildcard searches was inconsistent. Placeholders at the beginning or end of a search string caused string matching operators like CONTAINS to break and return incomplete results. Explicitly searching for characters that could be interpreted as wildcards was not possible. This was due to backwards compatibility to the swing client, which is no longer supported.

Some methods and constants for customizing have been removed​

What changed​

The following methods and constants have been removed:

db.exportData
db.fastExportData
util.ESCAPEMODE_ESCAPE
util.ESCAPEMODE_DOUBLE
util.ESCAPEMODE_CHANGE
util.ESCAPEMODE_NOTHING

Why it matters​

These were needed for the deprecated swing client. Removing them improves the maintainability of the existing code.