Commit e12a609a authored by Nicolas Dumazet's avatar Nicolas Dumazet

fix bug from r33320

We "uniqify" resource_uid,quantity_unit and not uid,resource_uid.
Thanks to dict keys, that should be now clearer than tuple[1],tuple[2]


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@33347 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent 7f4911a1
...@@ -78,7 +78,7 @@ getQuantityUnitConversionDefinitionRowList\r\n ...@@ -78,7 +78,7 @@ getQuantityUnitConversionDefinitionRowList\r\n
Make sure that we get no duplicates, and also aggregate the uids of the modified resources for deletion\n Make sure that we get no duplicates, and also aggregate the uids of the modified resources for deletion\n
</dtml-comment>\n </dtml-comment>\n
<dtml-in loop_item prefix="inner">\n <dtml-in loop_item prefix="inner">\n
<dtml-call expr="quantity_unit_conversion_dict.setdefault(inner_item[\'uid\'], {}).setdefault(inner_item[\'resource_uid\'], inner_item)">\n <dtml-call expr="quantity_unit_conversion_dict.setdefault(inner_item[\'resource_uid\'], {}).setdefault(inner_item[\'quantity_unit\'], inner_item)">\n
</dtml-in>\n </dtml-in>\n
</dtml-if>\n </dtml-if>\n
</dtml-in>\n </dtml-in>\n
...@@ -155,7 +155,7 @@ VALUES\n ...@@ -155,7 +155,7 @@ VALUES\n
Make sure that we get no duplicates, and also aggregate the uids of the modified resources for deletion\n Make sure that we get no duplicates, and also aggregate the uids of the modified resources for deletion\n
</dtml-comment>\n </dtml-comment>\n
<dtml-in loop_item prefix="inner">\n <dtml-in loop_item prefix="inner">\n
<dtml-call expr="quantity_unit_conversion_dict.setdefault(inner_item[\'uid\'], {}).setdefault(inner_item[\'resource_uid\'], inner_item)">\n <dtml-call expr="quantity_unit_conversion_dict.setdefault(inner_item[\'resource_uid\'], {}).setdefault(inner_item[\'quantity_unit\'], inner_item)">\n
</dtml-in>\n </dtml-in>\n
</dtml-if>\n </dtml-if>\n
</dtml-in>\n </dtml-in>\n
......
181 182
\ No newline at end of file \ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment