SQL only ViewObject with WhereClause

Question

I have a sql only viewobject. My query that makes this viewobject contains a where clause to indicate a join. The viewobject works fine but I cannot do the setWhereClause(string) to add on criteria if I want to search the view. It looks like bc4j doesn't know there already is a where clause started in the query and so it tacks on a new WHERE clause which makes a bad query.
Any suggestions on how to get around this?

Answer 1

Darko, we try hard to offer much more functionality (and advanced functionality) than a simple JDBC prepared statement.
I tried creating an expert mode SQL query:
SELECT DISTINCT EMPNO, ENAME FROM EMP.
Then at runtime I do:
vo.setWhereClause("ENAME LIKE '%'||?||'%');
vo.setWhereClauseParam(0,'A');.
and this works fine. The trick is that since expert-mode view objects get wrapped as inline views (to allow runtime appending of WHERE clause, actually), you need to select any column in the select statement to which you want to later refer in a dynamically-appended where clause.
If you want to prevent the inline-view wrapping, you can write the following code in your view object's ViewObjectImpl subclass to force the VO to NOT be treated as an expert-mode SQL VO.
  // Goes in your view object impl subclass
  public void create() {
     // Force this VO to NOT be treated as an expert-mode SQL, so that
     // its query does not get wrapped as an inline view.
     getViewDef().setFullSql(false);
  }I used this trick above to create an expert mode query like:
SELECT DISTINCT deptno FROM empand then at runtime I add a dynamic where clause that refers to a column
in EMP that is not in the select list like this:
    ViewObject vo = am.findViewObject("View1");
    vo.setWhereClause("ename like '%A%'");
    vo.executeQuery();
    System.out.println(vo.first().getAttribute(0));and this causes the query to come out as:
SELECT DISTINCT deptno FROM emp WHERE ename like '%A%'.
instead of:
SELECT * FROM (SELECT DISTINCT deptno FROM emp) QRSLT WHERE ename like '%A%'which would cause an error due to the fact that ename is not in the select list of the original (wrapped, inline) query.