<object class="modMenu" table="menus" extends="modAccessibleObject">
<field key="text" dbtype="varchar" precision="255" phptype="string" null="false" default="" index="pk" />
<field key="parent" dbtype="varchar" precision="255" phptype="string" null="false" default="" index="index" />
<field key="action" dbtype="int" precision="11" attributes="unsigned" phptype="integer" null="false" default="0" index="index" />
<field key="description" dbtype="varchar" precision="255" phptype="string" null="false" default="" />
<field key="icon" dbtype="varchar" precision="255" phptype="string" null="false" default="" />
<field key="menuindex" dbtype="int" precision="11" attributes="unsigned" phptype="integer" null="false" default="0" />
<field key="params" dbtype="text" phptype="string" null="false" default="" />
<field key="handler" dbtype="text" phptype="string" null="false" default="" />
<field key="permissions" dbtype="text" phptype="string" null="false" default="" />
<aggregate alias="Action" class="modAction" local="action" foreign="id" owner="foreign" cardinality="one" />
<aggregate alias="Parent" class="modMenu" local="parent" foreign="text" owner="foreign" cardinality="one" />
<aggregate alias="Children" class="modMenu" local="text" foreign="parent" owner="local" cardinality="many" />
<composite alias="Acls" class="modAccessMenu" local="text" foreign="target" owner="local" cardinality="many" />
</object>
Why oh why is this table unique on the menu title??
Since you support the perfectly fine multi-level menu (which we truly love) it is really
weird we cannot have multiple items with the same name but different parameters.
Just a case where this would be usefull:
* Webshops
* Shop 1
* Products
* Categories
* Orders
* Shop 2
* Products
* Categories
* Orders
With the current setup, this isn’t possible. Do you guys have a reason for choosing this setup? Or
did it just slip in?
If so i’d like a feature request on this...
Thanks in advance,
b03tz.
