I reported this bug last week.

Robert Shubert
Tronics

Ezra wrote:
I just installed the latest version of OSX Witango (5.0.1.061) and ran into an error with a taf which works fine on 5.0.1.054.

Single search action using custom columns and two tables with same field names results in SQL errors.


Example: Table 1 contains id,city,blah,blah2 Table 2 contains id,city,blah,blah2

SEARCH ACTION: (USING CUSTOM COLUMNS)
LOWER(M1.city) contains <@LOWER STR="<@ARG CITY>">
LOWER(M2.city2) contains <@LOWER STR="<@ARG CITY2>">

results in the following error:
[Error] 933 ORA-00933: SQL command not properly ended

Studying the log reveals:
WHERE ((CITY) LIKE '%toronto%'))

It seems like while using custom columns and same field names exists on two different tables, witango takes out "lower(M1.) away while executing search action and results in an error.

The same taf works correctly on .54 build.

Any body ran into this and have a solution?

thanks,
Ezra


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to