There appears to be a change in behavior in the Database.makePersistent
method. In OJB 1.0RC7 the Database.makePersistent class would update the
primary key field of the object being persisted (autoincrement) even
before the transaction was committed (I.E. right after the
makePersistent call). It a
i added
testOnBorrow="true"
validationQuery="SELECT 1"
to the descriptor, I'l wait and see what happens.
Dennis
2006/1/5, Thomas Dudziak <[EMAIL PROTECTED]>:
>
> On 1/5/06, Dennis Bekkering <[EMAIL PROTECTED]> wrote:
>
> > I asked my provider and they didn't change anythi
hi nicolas,
ojb just release 1.0.4. could you please try this as well ?
jakob
DELAHAYE Nicolas schrieb:
Sorry for multi posting,
Otherwise, the version we use is 1.03
Jakob Braeuchi wrote:
hi nicolas,
i recommend not to cross-post, and to post the same message only once ;)
further i re
Sorry for multi posting,
Otherwise, the version we use is 1.03
Jakob Braeuchi wrote:
hi nicolas,
i recommend not to cross-post, and to post the same message only once ;)
further i recommend to tell us the version of ojb you're using.
thank
jakob
--
Nicolas DELAHAYE
On 1/5/06, Dennis Bekkering <[EMAIL PROTECTED]> wrote:
> I asked my provider and they didn't change anything. They pointed out the
> possible absence of autoReconnect=true in my JDBC url. Does anybody knows if
> that might help. I'd rather have that than a ping query for every call.
Hmm, autoReco
hi nicolas,
i recommend not to cross-post, and to post the same message only once ;)
further i recommend to tell us the version of ojb you're using.
thank
jakob
[EMAIL PROTECTED] schrieb:
Hi,
It seems when i use a n-m relation to a subclassed object, the sql produced
by ojb is not good.
T
I asked my provider and they didn't change anything. They pointed out the
possible absence of autoReconnect=true in my JDBC url. Does anybody knows if
that might help. I'd rather have that than a ping query for every call.
Thanks,
Dennis
2006/1/4, Dennis Bekkering <[EMAIL PROTECTED]>:
>
> Thomas,
