In that case, mind if I open a long-term issue called
Connective constraints between fields?
For now I 've just implemented all 4 combinations (2^2 = 4)
as a separate rule and it works :)
With kind regards,
Geoffrey De Smet
Edson Tirelli wrote:
Geoffrey,
Mark already provided the
I don't know if we would ever do such a thing, to get something like
that working with Rete is really messy.
Mark
Geoffrey De Smet wrote:
In that case, mind if I open a long-term issue called
Connective constraints between fields?
For now I 've just implemented all 4 combinations (2^2 = 4)
Geoffrey,
Mark already provided the samples link, but it is important to note
that connective constraints allow multiple expression per field, not
between fields.
[]s
Edson
Geoffrey De Smet wrote:
I opened the first issue (bug) with testcase patch here:
Edson Tirelli wrote, On 2006-11-10 12:37 AM:
Hey Geoffrey,
You guys are doing a great job testing things. Thanks.
The correct syntax would be like that:
query multipleMatchesPerTeamPerDay
$team : Team()
Match( $id : id, homeTeam == $team, $day : day ) ||
Match( $id : id,
In 3.2 (trunk) we have added what are known as connective constraints which will do what you want (yes they are different from conditional elements in behaviour).But not yet, in 3.0 can you do that.
On 11/10/06, John Cocktolstoy [EMAIL PROTECTED] wrote:
Hi guys,I got the same errors but thought it
Hey Geoffrey,
You guys are doing a great job testing things. Thanks.
The correct syntax would be like that:
query multipleMatchesPerTeamPerDay
$team : Team()
Match( $id : id, homeTeam == $team, $day : day ) ||
Match( $id : id, awayTeam == $team, $day : day )
exists Match( id
