MDG/Problem extending/stereotyping UML::Tables

[RobG.]

I'm using Enterprise Architects 'Custom UML Profiles' to create an MDG for a particular type of technology that my company is developing. I have successfully extended several UML objects however have hit an issue when extending the UML::Table stereotype which itself appears to extend the UML::Class stereotype.

When I use my newly defined MyTableType Stereotype the DB Version field is not set. I can manually alter the 'Database' field when I create a new element from my MDG on the usual properties dialog, but it is not propagated through to the Table Details DB Version.

The result is that I am unable to define any table attribute's as no datatype is recognised, so the attribute datatype list is empty.

I am unable to see how to set the DB Version in the metaclass or stereotype class - and while EA understands my stereotype is a Table, it doesn't update the DB Version appropriately.

I've even tried hacking a trigger into the DB Repository but EA somehow overwrites it anyway as BLANK!

Has anyone seen/solved this before?

[qwerty]

I actually can't really help but seem to remember that some stereotypes from internal MDGs (like that <<table>>) have their own special spice only available to the Sparxians. There seems to be some hidden code related to those which is doing some magic you can't control.

If you don't get a useful answer here in time you'd better contact Sparx support to help you with that.

q.

[RobG.]

Thanks - That's quite annoying if that is the case as the documentation specifies that you can extend the UML::Table metaclass.

I'm not able to get the hacky DB trigger working either, while I have it setting the correct values EA isn't playing ball!

[KP]

Try: From the main menu, Settings > Database Datatypes, select a Product Name and tick the Set as Default button. I don't think it is possible to define a different value for a stereotype, though I can see how that might be useful.

[RobG.]

Hi.

To clarify, I AM able to set the Database type (for example MySQL), but the Table Detail table does not show a DB Version (should reflect MySQL), and when I try to add Columns/Attributes there are no attribute data types to select from (e.g. Int, Text, Float etc)

Thanks

[KP]

So did you follow my instructions from my previous post? And if you drop a plain Table from the Class toolbox onto a diagram, does it have a database set?

[RobG.]

So did you follow my instructions from my previous post? And if you drop a plain Table from the Class toolbox onto a diagram, does it have a database set?

Yes - the Table class object works as expected. It is not the Database type I have having a problem setting, rather once the database type is set, the DB Version on the Table Detail tab has no value set.

I'm certain this is a bug rather than how I have created my metaclass, and I have raised a support ticket with Sparx to see if there is any outcome

[RobG.]

I'm certain this is a bug rather than how I have created my metaclass, and I have raised a support ticket with Sparx to see if there is any outcome

Sparx have reproduced and raised a ticket: 14058271