[Fixed] No custom attributes possible on inheritance

0 votes
asked May 19, 2014 in Solved by kufi (290 points)
recategorized Oct 13, 2015 by ludek.vodicka

I can't get custom orm attributes working for Propel.

I have the following custom orm2.cfg:

<?xml version="1.0" encoding="utf-8" standalone="no" ?>
<ormd2-configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <orm-configuration name="Propel" caption="Propel ORM" image="logoPropel.png" >
        <attribute-types>
            <struct name="Inheritance" section="orm" help-url="">
                <attribute name="copy_data_to_child" type="string" />
            </struct>
        </attribute-types>
    </orm-configuration>
</ormd2-configuration> 

This creates the correct custom attribute on the inheritance, but it won't be saved and nor exported to the generated .xml file for Propel.

commented May 19, 2014 by Martin Freki Stradej Skipper developer (74,840 points)

I am not sure if the attributes for inheritances are supported by the Propel itself.

Can you please post how the resulting definitions should look like? I can fix the export based on this information.

2 Answers

0 votes
answered Jun 30, 2014 by Martin Freki Stradej Skipper developer (74,840 points)
selected Jul 30, 2014 by Martin Freki Stradej
 
Best answer

This function was implemented in the version 3.0.0.1099, and released to public today.

From version 3.0, ORM Designer was renamed to Skipper. You can download Skipper from the official website:
www.skipper18.com/en/download

0 votes
answered May 19, 2014 by kufi (290 points)

It's only important for concrete_inheritance.

<behavior name="concrete_inheritance">
      <parameter name="extends" value="Ad"/>
      <parameter name="copy_data_to_child" value="true" />
</behavior>

I can't add a custom behavior, as this just duplicates the behavior instead of adding it to the existing behavior.

commented May 21, 2014 by Martin Freki Stradej Skipper developer (74,840 points)

Thank you for the clarification.

This is now missing in the ORM Designer because the concrete_inheritance is handled differently than both other behaviors and other inheritances.

We will fix the export so the custom parameters are supported.

...