RE: [rules-users] 'from accumulate' doesn't work on multiple colu mns?..

------------- 3. Regarding the distinct, I'm not sure if it would be good to have such "feature". Need further discussion I guess. But on of the ways to work around that is just to have a "driver" fact. I mean, if "f1" means a financial account, for instance, have a Financial Account fact: -- End of quote Yes, that's how I'm dealing with it right now... But you (or Mark?) mentioned some time ago regarding similar issue ("Convert logic to DRL rules") that it's better to aviod this kind of 'indexing' and keep the data model 'flattened' since it'd allow for more optimizations on DROOLS side. In my case 'Record' fact has 6-7 fields and the type of rules I have would require to have such index on almost all these fields (which means I'd have to assert 'unique value' facts for each of the fields). So, I thought this kind of problem (as well as combination of unique fields) can be solved easily with having such keyword ('distinct' or 'unique' or smth like that). I think that even implementation should not be very difficult, since it would just require to get all facts of particular type and assert a new set of 'unique value' facts for each of the fields used in the constraint... Kind of preprocessing step. But I think such index (index of all fields within particular fact type) might already being created as part of other algorithms?... Vlad -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Edson Tirelli Sent: 07 March 2007 17:43 To: Rules Users List Subject: Re: [rules-users] 'from accumulate' doesn't work on multiple columns?.. Vlad, Trying to answer both of your e-mails in this one. 1. Right now, accumulate supports only a single Pattern (column), as you already realized. That is a limitation we want to remove before the next final release, but it is not done yet. I already know how to fix that, but didn't had the time to do it yet. We are working hard in the BRMS side now. If anyone is willing to help with that, I can provide the instructions on how to do the implementation for that feature. 2. Regarding matching the same fact multiple times in a single tuple, this is a configuration. In 3.0.x, the default is to not allow the same fact to be matched multiple times in a single tuple. In 3.1, the default was changed to allow multiple matches. That is why your tested matched multiple times. This is one of the BIG warnings we need to add to the upgrade documentation. 3. Regarding the distinct, I'm not sure if it would be good to have such "feature". Need further discussion I guess. But on of the ways to work around that is just to have a "driver" fact. I mean, if "f1" means a financial account, for instance, have a Financial Account fact: rule ... when FinancialAccount( $id : id ) Double( doubleValue > 0 ) from accumulate( Record( finId == $id, $f2 : f2, $val : value ) init( double sum = 0; ) action( sum += ( $f2 < 10 ) ? $val : -$val; ) result( new Double( sum ) ) ) then // do something end Hope it helps. []s Edson Olenin, Vladimir (MOH) wrote: -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 JBoss, a division of Red Hat @ www.jboss.com _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users