On 1/9/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
wel that didn't help now it looks like this and that still doesn't help.
What do I have to do? My customers go crazy over this and me too!!! I really
don't know what to do anymore. On production I didn't switch to
1.0.4because lazy loading
On 1/9/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
The whole thing looks like this now, I don't use 1.0.4 though on production.
Does the attribute do anything then. It runs on rc7.
The custom attribute is new in 1.0.4, so it won't do anyting in older versions.
I'd suggest you first update to
my driver was and is mysql-connector-java-3.1.5-gamma-bin.jar so I updated
to jdbc level 3. Will update to 1.0.3 tonight if lazy is still lazy.
2006/1/9, Thomas Dudziak [EMAIL PROTECTED]:
On 1/9/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
The whole thing looks like this now, I don't use
Armin,
It was the cache setting not the lazy loading.Fast as lightning again ;-)
Strange though that without caching the 2nd number of queries is less?
thanks,
Dennis
did you notice that the ObjectCache configuration moved from
OJB.properties to repository file between rc7 and 1.0.4?
You have
On 1/9/06, Zhong Li [EMAIL PROTECTED] wrote:
Our application runs for a few weeks, today I got exceptions, The strange
thing is, the application can query, delete and save, but not insert (
create new Object). We use OJB 1.0.3. From exception, it seems run out of
connections. But question is
everything is on 1.0.4 now. I also updated all my other libraries with the
latest. The jdbc level is 3, lets wait and see. If it still fails I will
have to modify the pool class(es) I guess.
2006/1/9, Dennis Bekkering [EMAIL PROTECTED]:
my driver was and is
