Added a key for the portal type of the object linked to the parent through the specialise relation.

This is usefull to know from which kind of rule a simulation movement cames from.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@4018 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/ERP5Catalog/sql/erp5_mysql/properties.xml

@@ -54,6 +54,7 @@
     <item type="str">translated_portal_type | translation/translated_message/z_related_translated_portal_type</item>
     <item type="str">translated_simulation_state | translation/translated_message/z_related_translated_simulation_state</item>
     <item type="str">variationCategory | category/category_uid/z_related_uid</item>
+    <item type="str">parent_specialise_portal_type | category,catalog/portal_type/z_related_parent_specialise</item>
   </property>
   <property id="sql_catalog_request_keys" type="tuple">
   </property>

product/ERP5Catalog/sql/erp5_mysql/z_related_parent_specialise.zsql

+<dtml-comment>
+title:
+connection_id:erp5_sql_connection
+max_rows:1000
+max_cache:100
+cache_time:0
+class_name:
+class_file:
+</dtml-comment>
+<params>table_0
+table_0</params>
+<dtml-var table_1>.uid = <dtml-var table_0>.category_uid
+AND <dtml-var table_0>.base_category_uid = <dtml-var "portal_categories.specialise.getUid()">
+AND <dtml-var table_0>.uid = catalog.parent_uid
+