Re: Select statement fails under Express, but works underForte when usi

Question

Hi there,
I have logged this with Forte and it as been recognized as a bug ( #46554 ).
The Express methods you need to look at if you want to modify this behavior
are :
1 - BusinessQuery.BuildQuery() starting at line 217
2 - SqlQuery.GetWhereText() starting at line 60
We have gotten around the problem by modifying what Express generates by
changing it from ( col1, col2 ) in ( select col1, col2 ... ) to ( col1 +
col2 ) in ( select col1 + col2 ... )
Just one thing i'm not sure that the '+' is standard on every DBMS for
concatenation.
We are using SQL Server 6.5
Hope this helps.
Christian Boult ([email protected])
Programmeur - Analyste
Influatec inc.
-----Original Message-----
From: Metcalf, Roger <[email protected]>
To: '[email protected]' <[email protected]>
Date: Thursday, May 06, 1999 1:55 PM
Subject: Select statement fails under Express, but works under Forte when
using DB2
Express sometimes (e.g. with nested windows) generates SQL with a select
subquery, e.g.
select x1, x2 from t1 where (x1,x2) in (select x1,x2 from t2.....)
This fails on DB2 with a message that the comma in the where clause (x1,x2)
is not allowed.
This works on Oracle.
Does anyone have a workaround or other suggestion?
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

joe.meszaros wrote:
(SELECT ? AS Id, ? AS UserBytes FROM dual)I suggest that you test to see if that statement and ONLY that statement works at all.
There are rules for bind variables and that statement certainly looks suspicious.
If you can't get that to work then the rest of the attempt is pointless.