[EMAIL PROTECTED] wrote:
Ok, I´ve just to rewrite all code with PB api, using Vector and
RemovalAwareCollection and it works
Try to use the ODMG instead of the PB API now.
That worked for me, too. But I had problems
using HashSet for collections (see previous
mail "Collection problem" from 07.
Ok, I´ve just to rewrite all code with PB api, using Vector and
RemovalAwareCollection and it works
But, why do not DList and ODMW work? I´ve seen DListImplementatio source
code and I don´t recongnize any piece of code to call ODMG (PB) api..
jose Galiana
> [EMAIL PROTECTED] wrote:
>
>>Hi,
>
[EMAIL PROTECTED] wrote:
Hi,
I´ve must be really stupid but, after read tutorials, eMails, source code...
I´ve not be able to run my 1:m code.
Two classes A and B, with A <--- B relation (1:m)
public class A
{
private int id;
private DList listB;
private String name;
public void A()
{
Hi,
I´ve must be really stupid but, after read tutorials, eMails, source code...
I´ve not be able to run my 1:m code.
Two classes A and B, with A <--- B relation (1:m)
public class A
{
private int id;
private DList listB;
private String name;
public void A()
{
listB = new D
ting objects.
[]s
Edson Richter
- Original Message -
From: "James Nyika" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 11:03 AM
Subject: Re: 1:m-relation
Edson,
see this is very interesting because i do not use any special
collection
thing about
auto-update
inserting objects.
[]s
Edson Richter
- Original Message -
From: "James Nyika" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 11:03 AM
Subject: Re: 1:m-relation
Edson,
see this is very interesting because i
use only if you need the
instances of B being removed when you store A... Nothing about auto-update
inserting objects.
[]s
Edson Richter
- Original Message -
From: "James Nyika" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 11:03 AM
Su
EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 08, 2003 4:46 PM
Subject: Re: 1:m-relation
Edson,
Can i ask you to give an example of how you add more B objects the
the
collection you described below
do you do something like this :
//get broker
broker = brokerfactory.def
Col().remove( 0 );
broker.store(a);
the item in 0 is deleted from database, as expected. This is a must for my
app.
Best regards,
Edson Richter
- Original Message -
From: "James Nyika" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 08, 2003 4:46 PM
Sub
PROTECTED]>
Sent: Monday, July 07, 2003 11:31 AM
Subject: 1:m-relation
i am working on a mysql-database and ojb rc3. i have an 1:m-relation
with
the following setting in the collection-desriptor of the parent
object:
auto-retrieve="true"
when i try to retrieve an parent-object i get the
. In this case, I'll recomendly you to
use cvs HEAD that has several fixes for these options over rc3.
Best regards,
Edson Richter
- Original Message -
From: "Christian Eugster" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 07, 2003 11:31 AM
hi christian,
imo you have defined the setter for your collection as Vector.
you should use Collection instead.
jakob
Christian Eugster wrote:
i am working on a mysql-database and ojb rc3. i have an 1:m-relation with
the following setting in the collection-desriptor of the parent object:
auto
i am working on a mysql-database and ojb rc3. i have an 1:m-relation with
the following setting in the collection-desriptor of the parent object:
auto-retrieve="true"
when i try to retrieve an parent-object i get the error-message as follows:
(setting auto-retrieve to false there i
it in ODMG api?
Thanks
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: 12 June 2003 14:17
>To: OJB Users List
>Subject: Re: 1:m relation not updating
>
>
>Hi again Shane
>
>Shane Mingins wrote:
>> Hi Thomas
>>
ng this factory method is the ODMG way to instantiate a DList.
cheers,
Thomas
Cheers
Shane
-Original Message-
From: Thomas Mahler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 11 June 2003 5:51 p.m.
To: OJB Users List
Subject: Re: 1:m relation not updating
You have to lock the b elements too i
an create a new DList
odmg.newDList()
Cheers
Shane
-Original Message-
From: Thomas Mahler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 11 June 2003 5:51 p.m.
To: OJB Users List
Subject: Re: 1:m relation not updating
You have to lock the b elements too if you are using normal collect
Sam
I was having the same problem that you were... could you possibly
email me your mapping of classes to tables
for the two classes. I would like to cross check that at least my
mapping configuration is similar to yours
thanks
James Nyika
Cambridge Technology Partners
The global eServices co
Thomas,
I am experiencing the same problem but i am not using to ODMG api (as
i think Saman was)
but rather straight PersistenceBroker.
1. Should i change my Vector collections to use DList ? or how do you
mean 'using DList' as your collection ?
2. WHen doing a proper 1-M mapping.. do i have
You have to lock the b elements too if you are using normal collections
to hold the many-side of the association.
If you were using DList as your collection class this won't be required.
cheers,
thomas
Saman Ghodsian wrote:
Hi there,
Here is the situation.. Say I have class A and class B
Hi there,
Here is the situation.. Say I have class A and class B 1->m
I created the repository.xml
Everything works fine when storing A to DB with a couple of B's
Tx.lock(a, Transaction.WRITE);
Tx.Commit
Next step is to load a and add more B's and then save it again.
I create
20 matches
Mail list logo
