WORKAROUND 1:
Manually add a global where clauses into the query in the end using SQL Editor.
WORKAROUND 2:
Use the following Global Where Clause to force your Oracle stored data to UPPER CASE for comparison.
Example:
UPPER( CUSTOMERS.NAME ) = 'JUST TENNIS'
This produces a Toad SQL Modeler SQL Statement of:
SELECT customers.cust_id, customers.NAME
FROM customers
WHERE ((UPPER (customers.NAME) = 'JUST TENNIS'))
Which produces the correct result
Warning: If an index is not being used on customer.NAME, while your performance may be just a bit slower to perform the UPPER conversion on the data table value, the return results should be correct.
But if an index is being used on customer.NAME, applying the UPPER function to the data column will shut off Oracle's ability to process the query using this index. This can greatly impact performance.
If the query MUST be processed based on an index on customer.NAME discuss the issue with the DBA about setting up an Oracle Function Based Index on the customer.NAME column. This feature was introduced in Oracle 8i and allows the result of the Oracle function to be indexed, not just the data itself.
Example: If the following index is created:
CREATE INDEX UPPER_CASE_OW_CUSTOMERS_NAME_IDX ON OW_CUSTOMERS (UPPER(NAME));
Oracle will store upper case data values, such as 'JUST TENNIS' in the index without impacting the actual data values in the table. The index can be used to search for 'JUST TENNIS' according to the query SQL Modeler generates.
STATUS:
This issue is fixed in Toad for Oracle 9.0. The latest version of Toad for Oracle can be downloaded here.
