I once started such a refactoring, but did not come very far, as the implementations differ quite a lot. Needs more effort...
[EMAIL PROTECTED] wrote:
I read up on Nested fields and I have a question about PersistentNestedFieldMaxPerformanceImpl and PersistentFieldMaxPerformanceImpl. After digging through the code it seems that PersistentNestedFieldMaxPerformanceImpl would behave the same as PersistentFieldMaxPerformanceImpl in cases when there are no nested fields specified. Is there a particular reason the two can not be merged into one? Is there a need for a PersistentField implementation that has to be explicitly not nestable?
Sincerely, Vladimir Berezniker Sr. Programmer Analyst Staten Island University Hospital
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
