Hi,
AW> I'm not very familiar with the OJB query generation, but I think you AW> should post the generated query (using p6spy or any other tool).
"SELECT A0.czz_id,A0.czz_glAtid,A0.czz_dokId FROM CzescZlozona A0,zp_czznd INNER JOIN ElementProjektowy A1 ON A0.czz_id=A1.ep_id WHERE (zp_czznd.czz_zp_zpIdnd IN (1)) AND A0.czz_id = zp_czznd.czz_zp_czpIdnd;"
Server: Msg 107, Level 16, State 2, Line 1 The column prefix 'A0' does not match with a table name or alias name used in the query.
If the query is auto-generated by OJB I think it's a dialect bug. In this case please make a detailed jira-bug report with stack trace, generated query and if possible with a fixed query statement (tested against your query browser).
AW> If you disable the collection proxy in the class causing the exception, AW> will the exception arise on main object materialization? AW> By the way why do you use useAutoCommit="2"? In non-managed environments AW> it's recommended to use "1".
setting proxy to "false" or useAutoCommit to "1" doesn't solve this problem :(
And you got the same stack trace? If yes, we can exclude problems with prefetching/proxy stuff.
regards, Armin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
