Hi, > > NO! You only need one persistent class Person. > > You can modify the existing class-descriptor for class > Person at runtime. > > that is for one query you remove all columns you don not > want to see from > > the classdescriptor. > > After finishing the query you restore the class-descriptor > to its original > > Form so that all other things work normally. > > And this will not influence e.g. other threads running in the > same vm that > is querying for class Person ? >
It will affect all brokers that use the same repository. You should be careful to do such things only on a repository that is *not shared* across multiple brokers. If you perform this operation after a PersistenceBroker.beginTransaction() call, this operation is threadsafe: A broker can only perform one transaction at a time. So once you open a tranaction on a broker instance, other threads won't be able to perform transactions on the same broker instance! cheers, Thomas > /max > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
