Hi Eric,

----- Original Message -----
From: "Eric Northam" <[EMAIL PROTECTED]>
To: "'OJB Users List'" <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 8:27 PM
Subject: RE: ODMG api with m:n mapping.


> Since it was an error on my part for setting auto-update="true" I'm
not sure
> you need the test. What result should the test be expecting?

if it now works for you, we don't need a new test ;-)

> It would
> probably more appropriate if an exception was thrown stating that
> auto-update must be set to false under ODMG and JDO.

I don't know if this can be easy implemented (without a
performance impact). Hope that we will find a way till
version 1.1 to make this differentiation unnecessary.

regards,
Armin

>
> Eric
>
> -----Original Message-----
> From: Armin Waibel [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 12, 2003 12:04 PM
> To: OJB Users List
> Subject: Re: ODMG api with m:n mapping.
>
>
> Hi all,
>
> there is a test case called ManyToManayTest.java
> in the test suite ([db-ojb]/src/test/org/apache/ojb/odmg).
> These tests all passed well. It would be a good thing
> if someone would add a new test to point out the
> problems (bug?).
>
> regards,
> Armin
>
> ----- Original Message -----
> From: "Eric Northam" <[EMAIL PROTECTED]>
> To: "'OJB Users List'" <[EMAIL PROTECTED]>
> Sent: Thursday, June 12, 2003 4:00 PM
> Subject: RE: ODMG api with m:n mapping.
>
>
> > Nope and I was able to duplicate the problem under Hypersonic albeit
> with a
> > slightly different error message.
> >
> > Eric
> >
> > -----Original Message-----
> > From: Henrik Berg [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, June 12, 2003 9:49 AM
> > To: OJB Users List
> > Subject: Re: ODMG api with m:n mapping.
> >
> >
> > Still no answers...???
> >
> >
> > Eric Northam <[EMAIL PROTECTED]> writes:
> >
> > > Has anyone come up with a solution for this? I'm having the same
> > > problem. I haven't tested whether it works with the
> PersistenceBroker
> > > though.
> > >
> > > Eric
> > >
> > > Subject: ODMG api with m:n mapping.
> > > From: Wara Songkran <paan130 <at> yahoo.com>
> > > Date: Sat, 24 May 2003 02:02:46 -0700 (PDT)
> > > Newsgroups:
> > >
<http://news.gmane.org/thread.php?group=gmane.comp.jakarta.ojb.user>
> > > gmane.comp.jakarta.ojb.user
> > > Reply-to: "OJB Users List" <ojb-user <at> db.apache.org>
> > >
> > > I'm working on non-decomposed m:n mapping. My code is
> > >
> > >
> > >
> > > ---------PersistenceBroker----------------
> > >
> > >
> > >
> > >         Car c = new Car();
> > >
> > >         Cylinder s = new Cylinder();
> > >
> > >
> > >
> > >         Collection col = new ArrayList();
> > >
> > >         col.add(s);
> > >
> > >
> > >
> > >         c.setAllSpareparts(col);
> > >
> > >         broker.store(c);
> > >
> > >
> > >
> > > ----------ODMG-----------------------------
> > >
> > >
> > >
> > >         Transaction tx = null;
> > >
> > >
> > >
> > >         Car c = new Car();
> > >
> > >         Cylinder s = new Cylinder();
> > >
> > >
> > >
> > >         Collection col = new ArrayList();
> > >
> > >         col.add(s);
> > >
> > >
> > >
> > >         c.setAllSpareparts(col);
> > >
> > >
> > >
> > >         try {
> > >
> > >             tx = odmg.newTransaction();
> > >
> > >             tx.begin();
> > >
> > >
> > >
> > >             tx.lock(c,Transaction.WRITE);
> > >
> > >             tx.commit();
> > >
> > >         } catch (LockNotGrantedException e) {
> > >
> > >             e.printStackTrace();
> > >
> > >         }
> > >
> > >
> > >
> > > when I use PresistenceBroker it's work fine but with
> > >
> > > odmg  api it cause error.
> > >
> > >
> > >
> > > [org.apache.ojb.odmg.ObjectEnvelopeTable] ERROR:
> > >
> > > Commit on object level failed for tx
> > >
> > > [EMAIL PROTECTED]
> > >
> > > Invalid argument value: Duplicate entry '121' for key
> > >
> > > 1
> > >
> > >
> > >
> > > I'm using mysql and all table is InnoDB.
> > >
> > >
> > >
> > > please help.
> > >
> > >
> > >
> > >
> > >
> > > DISCLAIMER: The information contained in this e-mail is, unless
> > > otherwise indicated, confidential and is intended solely for the
use
> > > of the named addressee. Access, copying or re-use of the e-mail or
> any
> > > information contained therein by any other person is not
authorized.
> > > If you are not the intended recipient please notify us immediately
> by
> > > returning the e-mail to the originator.
> >
> > --
> > Henrik
> >
>
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> > DISCLAIMER: The information contained in this e-mail is, unless
> otherwise
> > indicated, confidential and is intended solely for the use of the
> named
> > addressee. Access, copying or re-use of the e-mail or any
information
> > contained therein by any other person is not authorized. If you are
> not the
> > intended recipient please notify us immediately by returning the
> e-mail to
> > the originator.
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> DISCLAIMER: The information contained in this e-mail is, unless
otherwise
> indicated, confidential and is intended solely for the use of the
named
> addressee. Access, copying or re-use of the e-mail or any information
> contained therein by any other person is not authorized. If you are
not the
> intended recipient please notify us immediately by returning the
e-mail to
> the originator.
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to