ing? I'm very confused with
this function, when I enable it, it creates duplicate entries in the
database, of objects i'm updateing.
> - Can you give me a more detailde example, and maybe some source code?
>
>
> Here's is the original message:
>
>
Title: Re: [castor-dev] unable to call update
No doubt that Castor JDO is moving too slow. I really would
like to be an full time Castor developer, like I was. There is
really a lot of deadlines here, I don’t even have much “free”
time!!
The OQL side is certainly need test
Title: Re: [castor-dev] unable to call update
LOW
RULES!
I've
looked at his patches and code he's submitted and he's got the juice. Sign him
up!
m
btw
Low, what is the status of your JCA for castor project? Can you send me the
latest code?
-Original Message
Title: Re: [castor-dev] unable to call update
I
guess I'm worried because my Oracle patch never got committed (twice submitted)
I don't know who has commit status, and currently there are a bunch of bugs (ie
set-method, get-method) that made it into a release that should have been
Title: Re: [castor-dev] unable to call update
Hi Matthew,
There are three active part-times including me.
Working on a product without future, or will ever a
second-rated alternative doesn’t interest me to
spend my after work hours on it. And, I am spending
time on that
Message-
From: Julian Löffelhardt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 08, 2002 2:09 AM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] unable to call update
Hi,
The best way I found to avoid these (and many other) problems is:
Each Object implements the interface Persistent.
The