Messages

1

General Board / Re: Changing an attributes data type

« on: June 13, 2006, 05:05:57 am »

Yes, according to "http://dev.mysql.com/downloads/" MySQL-5.0 is the current stable release and 5.1 is beta in the moment.

Regards,

Sino

2

General Board / Re: Changing an attributes data type

« on: June 13, 2006, 04:13:56 am »

Sino,

You should be able to set up a trigger - I think this will work with either MySQL engine - to handle updates to the 'using' tables when a datatype is changed. EA has several tables with both primary and candidate keys, so this might help you elsewhere.

EA is pretty good about tolerating triggers and stored procedures layered on top of its base functionality.

That said, test (test, test, test...)

David

Thank you for your answer, Unfortunatelly we're still using MySQL 4.0, which doesn't support tiggers, views, procedures, ... :-(. Even sub-queries are not supported which let me run into some trouble the last two days (I've solved with a local install of mysql-5 on my personal computer and then importing a Backup from the original repository).
However, seems as I've to talk to my boss and ask him to upgrade the database engine.
Thanks again for your answer.

Best regards,

Sino

3

General Board / Re: Changing an attributes data type

« on: June 13, 2006, 01:35:03 am »

You've got the right columns there.  I just want to say to make sure you update the Type columns with the names of each type too.

Thank you for your reply, that was what I#ve expected.

Oh, and one more thing. If I try to change the data type of an operations parameter in the EA, but both have the same name, then EA won't do anything. e.g. the data type "CharacterString" was defined multiple times. Now I want to change in each operation the parameters type from the currernt CharacterString (which obviously doesn't exist anymore) to the sole existing version of CharacterString. After that I see in the database that the parameter still refers to the old non-existing data type. The solution currently is to first select another data type (having a different name) and after that select CharacterString again.
So is this a known Problem that EA compares data types by their names instead of their ID's?

However, think I'll do most of the changes on the database directly.

Thank you again for you reply.

Best regards,

Sino

4

General Board / Changing an attributes data type

« on: June 12, 2006, 08:41:20 am »

Dear all,
We are working with several partners on a project based on a mysql repository. Each partner defines one or more services which hence will work together. Till now every partner has defined data types (Such as collections, ...) by its own needs, which has lead to inconsistencies between the resulting services. Some weeks ago we've tried to harmonize that and we've defined a bunch of data types which shall be used when applicable (Only define new data types when needed). Already existing type definitions were deleted.
Now we've got the problem that operation parameters and class attributes still refer to the old data types, which in fact doesn't exist anymore. Our first thought was that each partner has to check for consistency within its own services. However, after we made a list of inconsistencies (operation parameters, return types and class attributes refering to non-existing data types), we've seen that's a big work to perform. So we thought about updating class attributes and so on by accessing the MySQL database directly (So we can update a bunch of attributes in one step without having to select each of them separately in the EA).
For updating the data type of a class attribute, I would simply update the following column:

t_attribute.Classifier

For the return type of an operation the following column
t_operation.Classifier

And last but not least the follwing column for updating an operations parameter.
t_operationparams.Classifier

So all I want to know is, if the columns shown above are the sole points where updates must be performed, or are there any other tables affected as well?
(The EA repository consists of 93 tables and I 'am not sure if there's somewhere an important link between those which I have overseen).

Best regards,

Sino

5

General Board / Transform UML to WSDL

« on: May 29, 2006, 02:52:22 am »

Dear all,
in our project we want to use the ability of the EA to generate WSDL based on UML models. Now so far we have a small problem. We are using the EA to specifiy alot of services, where each service is specified within an own sub-package. Data types needed by all those services are also contained in a separate package. To prevent any problems connected with that big project, I've started a new, very small project just to get rid of the "generate WSDL" funtion of the EA. Now my problem is that the generated WSDL file is correct if the data type definitions are within the same package as the service interface, but if the data type definitions are in a separate package (outside the service definition), the resulting WSDL document gots an empty <type> section.
So is there a way to get a WSDL document with a valid <type> section even if the data types are defined in a separated package? Haven't found anything related to that in the help yet .
Thanks in advance,

Sino

6

General Board / Re: Show non existing dependencies

« on: May 26, 2006, 01:57:14 pm »

I interpreted what they were wanting as the opposite.  After deleting a class out of the project view, keep showing it on diagrams (in red) so that it could be fixed.  ie. The object on this diagram has been orphaned from the object it's representing.

Yes, that's correct. We're woking with several partnerws on our repository and, to explain it a little bit more clearly,  there are currently two problems:


1. Orphaned types
Every partner is specifying its own service. Unfortunatelly we haven't defined a set of common types at the beginning and so every service editor has specified types by their own needs. At present we have defined a bunch of common types, where some were already defined by service editors (they defined them before because they had need them). We have deleted those of the service editors and told them to use the new defined one.
So in that case it would be very helpful if orphaned links would be highlighted in the diagrams rather than simply delete.

2. Undo
Since we are working with several partners on the repository, deleting a type from the project is regular (hoping that's the right word ;-) ). e.g. A partner want to delete an own specified type (they are still allowed to define types by themselve if they are not already specified in the common types), and clicks accidently on the wrong entry. In that case the only way to undo it, is to load the last backup into the data base, but in my opinion it should also be possible to simply do an undo as it is possible if woking on a diagram.

Best regards,

Sino

7

General Board / Re: Show non existing dependencies

« on: May 23, 2006, 03:07:13 am »

Thank you for your answer, that was something I've expected . Think I'll send a request about adding something as this in future versions (e.g. Used classes in a class diagram which doesn't exist anymore, could get highlighted in red color. So everyone working at that diagram could see what's wrong and update it. Simply deleting references when the object gets deleted is not a good idea).

Anyway, there's another question. When deleting an object in the "project view" (The tree like view) I can't use the undo function (I have not closed and restart the EA but simply deleted an object in the projects view and no undo is possible). The "undo" option in "Edit" menu is deactivated and it is only working if doing changes on a diagram, but not if doing something in the project view. So is there a way to make the undo function also working in the project View?

Thanks is advance.

Best regards,

Sino

8

General Board / Show non existing dependencies

« on: May 19, 2006, 07:52:32 am »

Dear forum,
unfortunatelly I run in some problems. Now we're working on a big project with several partners. Till now each partner has specified one or more services in an own sub-package and has specified needed data types (classes) by their own. Yesterday we came up with the idea to create a separate package holding all needed data types (There were several data types specified twice since of the need by several partners). However, after moving all the specified data types from the sub-packages of each service editor to the global package, I was asked why there are data types specified twice, and then I was told to simply delete those doubles. Unfortunatelly when deleting those, they were also removed from the existing class diagrams (which I've realized tody ) , including inheritance and dependency arrows.

We have a backup, but unfortunatelly this is two days old.
I assume there's no way to recovery the deleted classes? But perhaps there's a way to see in which class diagrams they were removed (Something as a history for each class diagram)? Can't believe classes are removed from all class diagrams without give the possibility to check where they was removed.

Best regards,

Sino