MAIL PROTECTED]
> Sent: 23 October 2003 13:47
> To: OJB Users List
> Subject: RE: refresh=true OR refresh=false
>
>
> Thank you. I supposed, from a performance perspective, if the
> relationship is ternary, I should have a convenience method that does
> the setA(A) and A.getBs(
Thank you. I supposed, from a performance perspective, if the
relationship is ternary, I should have a convenience method that does
the setA(A) and A.getBs().add(B) and then I can turn it off to stop the
SQL from being executed. Correct?
On Thu, 2003-10-23 at 00:32, Charles Anthony wrote:
> Hi,
Hi,
It is indeed to do with caching.
Let us have a one-to-many relation : A has many Bs.
We modify A (but leave it's related B's alone), and A remains in the cache.
We then create a B, and associate it with A (e.g. b.setA(A) ) - but we
*don't* add it to A's collection of B's.
If we then retrieve
