Messages

1

Bugs and Issues / Issue with t_snapshot and t_usys primary columns

« on: April 04, 2013, 02:44:04 am »

I have successfully managed to get Enterprise Architect working with MS SQL Server and am using transactional replication to allow users to work offsite or remotely without a connection, and synchronie when they are back in the office.

To achieve this, MS SQL Server needs to manage the primary ID's so it can assign and  update ID ranges to remove potential for conflicts, however the t_snapshot table has a VARCHAR primary ID, and as EA is automatically allocating a next ID pattern this is causing conflicts when users are offline.

t_snapshot appears to be used to track auditing, and this is where the issue occurs.

Can a fix/patch be created to create a primary ID for this table that is an INTEGER? I see no reason why any primary ID unless a GUID would need to be textural.

2

Automation Interface, Add-Ins and Tools / Re: MDG/Problem extending/stereotyping UML::Tables

« on: May 21, 2014, 07:10:07 pm »

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

3

Automation Interface, Add-Ins and Tools / Re: MDG/Problem extending/stereotyping UML::Tables

« on: May 21, 2014, 07:05:51 pm »

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

4

Automation Interface, Add-Ins and Tools / Re: MDG/Problem extending/stereotyping UML::Tables

« on: May 20, 2014, 07:37:49 pm »

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

5

Automation Interface, Add-Ins and Tools / Re: MDG/Problem extending/stereotyping UML::Tables

« on: May 19, 2014, 08:30:31 pm »

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!

6

Automation Interface, Add-Ins and Tools / MDG/Problem extending/stereotyping UML::Tables

« on: May 19, 2014, 07:29:57 pm »

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?