It appears that the priority value now has opposite meaning when compared to version 1.8. That is, when two or more records have the same dpid value in version 1.8 it appeared that the row with the lower value in the pr column would be looked at first. Now it appears that the higher value in the pr column is looked at first. Either way is fine but if it could be documented with the module that would be helpful.
It also appears that if the row matching the value being looked for is not the first row compared, the lookup fails. This is the same whether doing the lookup from the MI interface or in the script.
Log in to post a comment.