Hi, I'm using HSQLDB and I have the same problems. It's for sure a bug in OJB. I'm considering not to use n:m relations anymore, maybe I can avoid n:m and redesign my database model. But for me it's also strange that such an important feature is buggy.
I had also other problems but that might be because of my faulty configuration. I used in the connection-descriptor in repository.xml jdbc-level="1.0" to be on the safe side, but since I'm using jdbc-level="2.0" some problems were gone. I think I'll stay with ODMG because I don't think that this bug is in the persistence layer and not in the ODMG API layer - in other words: I think it wouldn't help to migrate to PersistenceBroker API. I'll keep on experimenting and I'll keep you updated. /olaf [EMAIL PROTECTED] wrote: >Hi, >Thank you for writing. > >Is this a problem with ODMG and Oracle or is it independent > of the DataBase? >Because it is a very important feature and it's strange to > have a bug like this. > >Did you find many bugs in ODMG or only this? I am deciding > wich way I'm going to take with the project yet... > >Thanks. > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
