| Summary: | Runtime parameters: Allow for making free text and date fields optional without the need for users to enter % | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Shane Sammons <ssammons> |
| Component: | Reports | Assignee: | Galen Charlton <gmcharlt> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 - low | ||
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
Something you can do as a work around:
WHERE xxx LIKE CONCAT('%',<<search term>>,'%')
This way the users don't have to add the %.
We also have :all now, that works on drop down lists and adds an entry with % that is pre-selected. Having a % for date or free text is probably not as easy to resolve. |
Add a second field tag (placeholder / runtime argument) similar to <<>>, but it would user a logical check for no value and would either omit the argument (harder would require something like a regex removal) or put in the "%" for the end user. I was thinking something like <{}>, <[]>, <()>.