On Fri, 20 Feb 2004 14:13:40 +0100 Mahler Thomas <[EMAIL PROTECTED]> wrote:
> I think that you encounter an interference of the cache.
> Please try if clearing the cache right before the secong OQL query solves
> the problem.
How can I do this? (It won't work with the ODMG API, of course.)
> If this is the case I think using the PerBroker cache implementation should
> solve the issue.
I tried the ObjectCachePerBrokerImpl cache implementation, but I am loosing circular
references then.
Shouldn't a cache be transparent to the application? Not necessarily in terms of
access time or memory consumption, but in terms of *behaviour*?
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
