RE: BUGREPORT : OJB 1.0.5rc1 : UserAliases in OrderBy clauses are not replaced by the generated aliases for the joins resulting in illegal SQL statements

Hi, The management summary answer to your question "is it important to support alias-names in order by and having clause" is : Yes, it is really really really important!!! So now for some background information explaining our situation. We implemented a concept to support non-modelled (abstract)

Optimizing object materialization for 1:N relations

Hi, we are using OJB-1.0.1 and evertything works fine. Now I have the following situation: We have a security-mechanism which uses the classes ACL (AccessControlList) and ACLEntry. One ACL has many ACLEntries. Now when using the standard OJB-Materialization methods OJB uses 2 SQLs to mater