[Libreoffice-bugs] [Bug 42120] optionally treat filter values as matching patterns

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=42120

Lionel Elie Mamane <lionel at mamane.lu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
  Status Whiteboard|                            |ProposedEasyHack
                   |                            |DifficultyInteresting
                   |                            |SkillCpp
         Resolution|NOTABUG                     |
           Severity|normal                      |enhancement
           Priority|medium                      |low
         Depends on|48807                       |
             Blocks|                            |48807
     Ever Confirmed|1                           |0
            Summary|Form based filters not      |optionally treat filter
                   |functional in database      |values as matching patterns

--- Comment #6 from Lionel Elie Mamane <lionel at mamane.lu> 2012-04-18 02:30:55 PDT ---
As per request in comment 4 of bug 48807, changing to enhancement request.
Here's my summary of what the enhancement could look like:

 - Introduce a way so that values typed in a field in "filter form by form" or
in a "condition" line of query's design mode are treated as patterns to match
instead of as values to match. That is, if one types "A", the generated filter
(query WHERE clause) is "colName LIKE 'A'" and not "colName = 'A'".

 - That way should be *optional*. Should it be a global preference (in
tools/options/base)? A per-form/query checkbox somewhere (e.g. next to "execute
query directly" and in the navigator, respectively) ?

 - IMO the only sane way is that the decision to treat as value or as pattern
is made at the time the value is typed; if the checkbox is changed, all typed
values stay as they are. That is, if the option is enabled, and one types "A",
then it is immediately (and visibly) changed to "LIKE 'A'".


Open questions:

 - Should this happen for all column (field) types or e.g. only for (var)char
columns? Does it make much sense to filter a numeric column by pattern?


My opinion about this enhancement request: if people want it, I'm not really
opposing it, but I'm also not quite championing it.

I *strongly* require that "filter by form" and "request design mode" behave
coherently, that is the change should not be done for only one of them.

Also, could be an EasyHack.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.