Author |
Topic  |
|
fdranguet
France
82 Posts |
Posted - 02/25/2009 : 00:09:07
|
Hello,
I am trying to write a ROLAP report. It is based on a DB2 connection which is working fine (I have been able to write an SQL report without problem).
The problem is, when you try to retrieve data from a table having a field containing spaces, it is failing. I found out the SQL code generated lacks the quotes before the field names. Example of automatically generated SQL by ReportPortal:
SELECT Avg(OB.Prix de vente EUR) as "Prix De Vente Eur" FROM MVXCDTALIV.ORDERBOOK OB
That should have been:
SELECT Avg(OB."Prix de vente EUR") as "Prix De Vente Eur" FROM MVXCDTALIV.ORDERBOOK OB
(if I launch the second one on my DB2 database it is working fine).
It is a bug from ReportPortal, or is that I missed some place where you set a field separator or something like that ?
Many thanks for your help !
Regards, François Dranguet Scott Bader SA |
|
admin
1644 Posts |
Posted - 03/09/2009 : 14:58:51
|
Build 161 should have resolved this problem. |
 |
|
fdranguet
France
82 Posts |
Posted - 03/11/2009 : 00:47:12
|
Hi,
thanks for this fix, but this is only half-solved actually: now, on the select statement, field names are appropriately encapsuled into quotes; but that is not the case for other clauses on the query. For example, on the "JOIN" one, or the "WHERE" one, fields are not correctly encapsuled. Below an example of an error message I get:
SELECT Avg(OB."Coût Unitaire EUR") as "Coût Unitaire Eur" FROM MVXCDTALIV.ORDERBOOK OB INNER JOIN MVXCDTALIV.ORDERBOOK d4 ON d4.Identifiant ligne = OB.Identifiant ligne
The problem here is the field "Identifiant ligne", the SQL query should have been:
SELECT Avg(OB."Coût Unitaire EUR") as "Coût Unitaire Eur" FROM MVXCDTALIV.ORDERBOOK OB INNER JOIN MVXCDTALIV.ORDERBOOK d4 ON d4."Identifiant ligne" = OB."Identifiant ligne"
It is also the same situation for queries launched on filters.
Thanks for your help !
Regards, François Dranguet Scott Bader SA |
 |
|
admin
1644 Posts |
Posted - 03/13/2009 : 21:08:38
|
The fix to the join problem will be available in the next build (162). Please contact support@ReportPortal.com if you need a hot fix.
|
 |
|
|
Topic  |
|
|
|