Jakob Braeuchi wrote: > hi christof, hi,
> have you tried auto-update=true ? Yes i already set auto-update=true as you mentioned in your last mail. This made it possible to store objects of type B (the repository.xml is shown in one of my last mails). when auto-update is set to false, only parts of the object are stored in the database. But when i select an object from the database the members of the super class are set to null in both cases. These values aren't even looked up in the database (according to the select statements sent to the database). Stupid question, this is not the way it is supposed to work, is it? > the problem is imo that this must be false for odmg :( But it seems to work nonetheless. At least i can see no difference except for the fact that storing objects works if it is set to true. Thanks for any advice or suggestion christof > > jakob > > Necro wrote: > >> Jakob Braeuchi wrote: >> >> >>> hi christof, >>> >>> this is a problem with your auto-update setting in the >>> reference-desriptor pointing to the superclass. >>> auto-update should be true. >>> >>> >> >> Hi, >> >> thanks, now inserting a value works just fine. But now I got >> another problem. When I select an object of class B only the >> members of B are set, all members inherited from A are set >> to null. I tried to set auto-retrieve to true, but that does >> not change anything. >> >> I found a testcase in the class AnonymousFieldsTest, which does >> something similar i want to do. Could it be that this does not >> work with the odmg interface? >> >> What can I do? >> >> Thans in advance >> >> christof --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
