left join CTEEntity bug

[srx5223113]

CriteriaBuilder cb = cbf.create(entityManager, Tuple.class)

            // first step: create CTEEntity
            .with(TestBCTEEntity.class)
            .from(BEntity.class)
            .bind("id").select("id")
            .bind("code").select("code")
            .bind("name").select("name")
            .end()

            // second step: xxxJoin CTEEntity demo

            //  -------------demo1: inner join CTEEntity expected right.
            //.from(AEntity.class, "a")
            //.innerJoinOn(TestBCTEEntity.class, "b").on("a.bcode").eqExpression("b.code").end()

            // -------------demo2: left join CTEEntity when using CTEEntity where expressions expected right.
            //.from(AEntity.class, "a")
            //.leftJoinOn(TestBCTEEntity.class, "b").on("a.bcode").eqExpression("b.code").end()
            //.where("b.name").eq("testname")

            //  -------------demo3: left join CTEEntity without CTEEntity where expressions expected error.
            .from(AEntity.class, "a")
            .leftJoinOn(TestBCTEEntity.class, "b").on("a.bcode").eqExpression("b.code").end()
            ;

            Object o = cb.getResultList();

Above is demo code for using leftJoin/innerJoin CTEEntiy. in case demo3, there was an error would be happend, and other cases were correct. It indecated that it didn't identify CTEEntity when left join CTEEntity and without CTEEntity where expressions.
The error is: ...... left join (select * from TestBCTEEntity) zfec2_0 on (null is null and 999=999 and ......

[jwgmeligmeyling]

Demo 2 and 3 share the exact same code?

[srx5223113]

the only difference between demo2 and demo3 is demo2 has CTEEntity where expression, so demo2 can identify CTEENTIRY,but demo3 cann't.
so amazing.