From: Gavin K. <ga...@ap...> - 2002-11-06 14:20:42
|
> Currently I have another problem with the OuterJoinGenerator: > The SQL created by the constructor of EntityLoader is always using ' LEFT OUTER JOIN' > even if I use the OracleOuterJoinGenerator. I've added the a log statement in the constructor > and it tells me that the sql 'select .... from foo left outer join bar on ....' was created with > an OracleOuterJoinGenerator???!!!? I'm not following properly..... MultiTableEntityPersister produces some SQL with "left outer join" hardcoded, as you noted. Some refactoring is needed to fix this. But I'm pretty sure the SQL generation for outerjoin fetching never produces "LEFT OUTER JOIN" when the SQL dialect is set for Oracle. Surely you aren't seeing this when using EntityPersister? > In the documentation you mentioned clustering capabilities, but I haven't found any > code about it. The reason Hibernate is safe for use in a cluster is that by default caching is done at the transaction-level. We do not support the use of cross-transaction caching in a clustered environment, though Christian Muenier might be releasing some code for this is a seperate project. |