Hello Armin, we went for this approach. We have two descriptor repositories now, describing the same tables and referring to the same classes. The only issue is: The update of the one object (using descriptor repository 1) and the insert of the new object (using descriptor repository 2) have to occur within one transaction (naturally). To achieve this, we added the method setDescriptorRepository(DescriptorRepository descriptorRepository); to the PersistenceBroker interface. Now we can change the descriptor repository whenever required. It works so far, but we're not sure if this has other impacts. Is this a safe solution? What about officially adding the above method to the PersistenceBroker interface? Or better: are there plans to support updating only specific columns? I can imagine many users would want this, just think of tables with many and/or large columns and you want to update only one (perhaps in a batch-job...).
Thanks for help, Norbert. -----Original Message----- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 09. Oktober 2003 14:09 To: OJB Users List Subject: Re: Choose columns to update Hi, don't know if this will help you. With MetadataManager you can handle different metadata repositories (on per thread base), thus it's possible to have different ClassDescriptor for the same class (e.g. one with all fields, one with special fields). regards, Armin On Thu, 9 Oct 2003 13:07:10 +0200, <[EMAIL PROTECTED]> wrote: > Thanks for your reply. > > Could you please give me a hint how to achieve this anyhow? > We're planning a dirty workaround: Having a class with a static method > called by PersistenceBroker store(Object, ObjectModification) after > retrieving the class descriptor. > That method clones and modifies the affected class descriptor as desired, > depending on the object processed. The risk: If somewhere in the > framework > the class descriptor is not passed as parameter but instead looked up > from > the repository again, we're lost. > > How safe is this approach? Any other idea is highly appreciated. > > Thanks, > Norbert. > > > -----Original Message----- > From: Charles Anthony [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 09. Oktober 2003 12:04 > To: 'OJB Users List' > Subject: RE: Choose columns to update > > > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] >> Sent: 09 October 2003 11:01 >> To: [EMAIL PROTECTED] >> Subject: Choose columns to update >> >> >> Hi all, >> >> I need to tell OJB which columns to update when persisting an object >> (instead of updating all mapped fields). Can anybody please >> tell me how to >> do this? > > Hi, > > I'm sorry no-one replied before. > > In short, this is not currently possible with OJB. > > I have a sneaking suspicion that this is *not* a trivial thing to do; as > you > may have noticed from the list, the developers are currently trying to > work > towards a 1.0 release in the near future (maybe via an rc5) - such a > substantial feature request would be unlikely to make into a release in > the > near future. > > Of course, I may be talking complete rubbish - in which case one of the > committers should respond - but I thought I'd reply just so you don't > think > we are ignoring you on purpose. > > Cheers, > > Charles. > > > This email and any attachments are strictly confidential and are intended > solely for the addressee. If you are not the intended recipient you must > not disclose, forward, copy or take any action in reliance on this > message > or its attachments. If you have received this email in error please > notify > the sender as soon as possible and delete it from your computer systems. > Any views or opinions presented are solely those of the author and do not > necessarily reflect those of HPD Software Limited or its affiliates. > > At present the integrity of email across the internet cannot be > guaranteed > and messages sent via this medium are potentially at risk. All liability > is excluded to the extent permitted by law for any claims arising as a > re- > sult of the use of this medium to transmit information by or to > HPD Software Limited or its affiliates. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
