The bug/problem is, that SAPDB seems to put the columns like lower(jh.name) into the result-table three times each.no comment on this one?
i wasn't abled to reproduce the fact with smaller statements, so i guess it must be something about the above statement.
i also tried to explicitly select the columns into the result set, but statements like
SELECT lower(column) as test FROM table WHERE test like 'b%'
fail, because the column test cannot be accessed from the WHERE clause. Even HAVING failes.
i'd really need to know if i can work around this with another query (without a sub-select if possible) or if this is a bug in the SAPDB.
Thx
Sven
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
