This patch fixes the problem described in post 2 triggers on same key...causes "Unable to get value for functionid" on "Feedback for alpha and beta versions" Forum.
This problem arises when you use 2 or more triggers with the same function definition. Functions are stored in an sql table , and you can have multiple rows in this table with same functions definition. When you create a new trigger, you create a new row with the lastvalue field empty. When functions are evaluated, if the function's value hasn't changed in the sql table, rows are not updated. => "Unable to get value for functionid"
The patch proposes to fetch every different values for (function,parameter,itemid,lastvalue) instead of (function,parameter,itemid).
This problem arises when you use 2 or more triggers with the same function definition. Functions are stored in an sql table , and you can have multiple rows in this table with same functions definition. When you create a new trigger, you create a new row with the lastvalue field empty. When functions are evaluated, if the function's value hasn't changed in the sql table, rows are not updated. => "Unable to get value for functionid"
The patch proposes to fetch every different values for (function,parameter,itemid,lastvalue) instead of (function,parameter,itemid).