Columns in upper case, not setting column stereotype.

[serchgt]

Hello, my company have been using EA for years, and I'm new using it, most users have version 8 or 9, but I got installed 12.  And nobody can help me, seems to be a feature/bug for this version.

The scenario:

I got some entities defined as <class> then I changed properties to stereotype <table> and Database <Oracle>, the classes already had some attributes without stereotype.

So the problems I have are:

1. When I add any column/attribute it will automatically go uppercase, so if I add CustomerId it changes to CUSTOMERID.  If I change any of the previous properties before I changed to table, still keep in lower/upper case.

2. I have configured to "Group Attributes by Stereotype", so I checked if I add new columns, they become <<column>> but, if I modify previous, they stay without stereotype.


End line

I went with a coworker with those previous version of EA, and he in fact can use upper/case on columns without problem, and when he edited any of those without stereotype, program automatically add the <<column>> stereotype.

Maybe a noobish question, but I have already double checked Tools/Options and find nothing.

Thank you in advance.

[Geert Bellekens]

I'm sorry but I don't see the problem. Seems like EA is acting in a sensible way to me.

Geert

[RoyC]

What are you actually doing? Are you using the Database Builder? A few details on your approach might help us explain what is happening, and whether or not it should be happening.

[serchgt]

I use the Project Browser and the Diagram if the table is in there, let me put you some images.

There is an example where I put the name testField and when focus is out of that, the name I entered turn into all upper case.  There are other with the right name with lower case.

And the third image, when I do a new table all attributes are <<column>> or if I add new ones, but if I modify any "old" attribute from the table, it will don't change the stereotype, and if a coworker do, EA with automatically change to the correct stereotype (I cannot find a way to do it manually either).

Thank you


Putting testField
https://www.dropbox.com/s/6qpwfjxrfbibfea/Screen%201.png?dl=0

It turns automatically upper case
https://www.dropbox.com/s/h0wsmgj26n3ifeb/Screen%202.png?dl=0

This example some have stereotypes, and some don't (those that have were modified by coworker)
https://www.dropbox.com/s/4zsawvcsj1v3sro/Screen%203.png?dl=0

[serchgt]

Sorry to be so noisy.  I found a temporary solution, but wish I can find the proper way to fix it.

I change the entity class from "table" to blanks, so when I go to attributes now appears and can select the stereotype I wish (column) and also let me put the names with lower case.

Still have to switch clases between blanks and <table> everytime I need to do a change.

Attributes when Class with stereotype <table>:

Name - Type - Length - Scale - PK - Not Null - Alias

Attributes when Class with stereotype blanks:

Name - Type - Scope - Stereotype - Alias - Initial Value


Thank you.

[KP]

Perhaps what you need is the DDL transformation. Select the package that owns your class elements and right-click > Advanced > Transform Package, then select DDL. This will create a table element for each class while leaving your class model intact.

[serchgt]

Thank you KP, I just checked and it worked as you said.  Still not what I wished but another way to solve it.   

Thanks again!

[Infyrana]

Same problem here.. anyone having found a proper solution yet?
The sterotypes <blank> workaround really is just annoying and a lot of overhead, I really don't want to do this whenever I change a column name or add a column to a table.

I get that a lot of people might think "so what", but it really bothers me and I don't get why this behavior in the tool has been changed at all and still think it is a bug.

[Geert Bellekens]

Same problem here.. anyone having found a proper solution yet?
The sterotypes <blank> workaround really is just annoying and a lot of overhead, I really don't want to do this whenever I change a column name or add a column to a table.

I get that a lot of people might think "so what", but it really bothers me and I don't get why this behavior in the tool has been changed at all and still think it is a bug.

Maybe you specify the problem you are experiencing. There were a few listed in the thread.

Geert

[Infyrana]

Same problem here.. anyone having found a proper solution yet?
The sterotypes <blank> workaround really is just annoying and a lot of overhead, I really don't want to do this whenever I change a column name or add a column to a table.

I get that a lot of people might think "so what", but it really bothers me and I don't get why this behavior in the tool has been changed at all and still think it is a bug.

Maybe you specify the problem you are experiencing. There were a few listed in the thread.

Geert

Sorry, totally skipped the other problems in my head automatically.

I am talking about adding a new column to a class of type table / Oracle (or changing an existing columns name) will always convert the column name to upper case automatically.

EA build 1230 btw.

[Geert Bellekens]

Isn't that standard behavior for Oracle to store everything in UPPERCASE? So it seems like a good thing to me if you are modelling Oracle tables.

If you are however not modelling tables, but a logical data model, you should instead be creating classes and use the MDA transformations to make it a database model.

Geert

[Infyrana]

What I do in my project is just adding columns to some of the already existing tables, which are already stored as oracle tables in my base EA project, there's nothing I can change about that.

Oracle stores everything in upper case since forever, as far as I know, but until EA version 11, I was happy to at least being able to easily read my table column names in my design file. We unfortunately have column names consisting of several words. In upper case, this really is hard to read. And I simply don't think there is a need to override how a user wants to store a column name in this tool, no matter what Oracle will do later on.