Community
Participate
Working Groups
Description: Duplicate parameter are added Build number: 2.3.0.v20080429-0946 1.6 v20080428-0500 Steps to reproduce: 1, New a datasource FROM "BIRT Classic Models Sample Database" Connection profile 2, New a dataset based on the datasource 3, Add a table and input a condition to CUSTOMERNUMBER=:a 4, Modify the value to :A 5, Click Finish and check the parameters in Parameter page Expected result: Only one parameter in the page Actual result: There are two parameters: a and A. Error log:
This problem is actually with the SQB tool and its updates of the SQL Query model. It should be reproducible directly in SQB (independent of BIRT's integrated version). The use case is specific to editing a parameter variable name, e.g. from ":a" to ":abc", in the Conditions tab (under the Value column). The QueryStatement model is then updated with the correct SQL (i.e. getSQL() contains the correct condition clause with the revised parameter variable name. But the call to StatementHelper.getAllVariablesInQueryStatement( queryStmt, false ) returns 2 parameter variables (i.e. both the old and new variables). This problem does not exist when editing the parameter variable name directly in the Source pane.
Extending the above use case, i.e. after changing the host variable name in Conditions tab, if one then executes the "Run SQL" action, the problem does not exist. This is probably because the ExecuteAction triggers the SQLBuilder to reparse, which updates its QueryStatement. It seems that any updates made to the SQL query text through the Conditions tab should have automatically triggered it to reparse as well.
Removing SQB: prefix on bug title at PMC request
I tried to reproduce this error, but could not: DTP 1.6.1 20089019
I'd tried it with latest 1.6.2M1, and also not able to reproduce it anymore. I see that in the Conditions tab, it no longer allows one to edit an existing variable name directly in the cell. Perhaps that change has avoided the previous issue. Tianli, can you please try to see if it is still producible for your use case?
I have tried int the latest build and can not reproduce it. So it's good, the issue has been resolved.
This issue appears to have been resolved.
Closing