Bug 1249704 - Parameters do not work with LIKE in BASE
Parameters do not work with LIKE in BASE
Product: Fedora
Classification: Fedora
Component: libreoffice (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-03 11:27 EDT by John Griffiths
Modified: 2015-08-04 03:23 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-08-04 03:23:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Document Foundation 46207 None None None Never

  None (edit)
Description John Griffiths 2015-08-03 11:27:25 EDT
Description of problem:
Parameters do not substitute correctly when using the LIKE keyword in a WHERE clause of a query.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a query using LIKE without a parameter and execute it. It returns records.
2. Substitute a parameter for part of the LIKE.
3. Execute it. Receive error.

Actual results:
Get error. Using More from error dialog shows 

"SQL Status: 22023

The column index is out of range: 1, number of columns: 0."

Expected results:
Data should return.

Additional info:
Here are two queries. One without parameter that works and one with that does not work. The parameter is prompted for by LibreOffice, the query is just not executed properly.

SELECT "first_name", "last_name", "spouse", "address", "ml_num", "ml_address" FROM "floridasun"."contacts" "contacts" WHERE lower("address") like '%' || 'venice' || '%'

SELECT "first_name", "last_name", "spouse", "address", "ml_num", "ml_address" FROM "floridasun"."contacts" "contacts" WHERE lower("address") like lower('%' || :address || '%')

Note You need to log in before you can comment on or make changes to this bug.