One latst piece of information before I let this go for the moment.
Some of the examples of when you must use Column names, and when you
MUST have Escape Processing OFF is dependent not only on theHSQL
statement but on WHICH data type is passed in.
The date to string functions are this way. F
Hallo Frank
No issue for now then. Perhaps it is more fitting in user faq
document.anyway.
Andrew
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Andrew.
Change the select statement to
SELECT CASE DATA WHEN '' THEN 'X' WHEN '' THEN 'Y' WHEN ''
THEN 'Z' ELSE '
Hi Andrew.
> Change the select statement to
>
> SELECT CASE DATA WHEN '' THEN 'X' WHEN '' THEN 'Y' WHEN ''
> THEN 'Z' ELSE 'NOTFOUND' END AS "DATA" FROM TESTCASE
>
>
> It still requires that EscapeProcessing = false.
The HSQLDB engine is capable of more things that OOo's cross-DB
Well, found the solution.
Change the select statement to
SELECT CASE DATA WHEN '' THEN 'X' WHEN '' THEN 'Y' WHEN ''
THEN 'Z' ELSE 'NOTFOUND' END AS "DATA" FROM TESTCASE
It still requires that EscapeProcessing = false. With the change
(explicity setting the return columns name )
Installation WinXP SP2, OO.o 1.9.123
I am experiencing rather odd behavior between queries and viees when
using case when and coalese commands.
Here are the steps to reproduce the effect.
Created HSQL embedded datasource using build 1.9.123
Execute the following commands in the sql window. T
