Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - bholtzman

Pages: [1]
1
General Board / Visio import: Element text invisible
« on: July 10, 2018, 07:42:00 am »
Hi all,
I am trying to import some Visio diagrams into an instance of EA on Amazon Web Services which uses a MySQL database. I used the MDG Link for Microsoft Visio within EA 14 (Build 1421). I opened my diagram to find a number of issues:
1. default style is hand drawn mode
2. there don't seem to be any connectors
3. the text inside each item is not visible

Item 1 is easily addressed.

For item 2, I did some checking inside the database as I have SQL access. I ran this query (after identifying package_id 305 as the import):
select * from t_connector where start_object_id in (select object_id from t_object where package_id = 305) or end_object_id in (select object_id from t_object where package_id = 305)

The result set was null, so I concluded that no connectors were created.

For item 3, I found that each element was of type Rectangle and stereotype rectangle. I found that if I null the stereotype, the Element Name text suddenly appears. I attempted to make the change using an SQL update to a different element:
update t_object set stereotype = null where object_id = 9717

But this did not make the Element Name text visible.

I searched all through the t_ tables in the database but could not figure out where the data is stored that makes the text visible. When you change the stereotype of an element to null using EA, where does that change appear in the database other than in the stereotype column of t_object? I noticed that once you do that the Element Type in the Element Properties window changes to Class.

I ran SQL to select all from t_object to fetch only the two elements of interest, the one I whose stereotype I changed to null using EA and the one whose stereotype I changed to null using SQL. I could not detect any difference.

Any thoughts or insights? Thank you.

Bill


2
General Board / Insert tagged value from MS Access
« on: August 10, 2017, 01:54:22 am »
I've built a tool in MS Access that connects to the EA database and provides tracking and a custom metadata "overlay". The tool can export a combined set of EA and non-EA metadata in various custom formats. One of the data elements I am extracting is from the two tagged value tables in EA, t_attributetag and t_objectproperties.

I have limited the Access app to querying the native EA tables only. I have never done any inserts from the Access app, but I have selectively run a few table updates manually.

The question has now come up as to whether new tagged value entries can be made from the Access side. Is that a bad idea or is it doable with careful diligence? Is there a way to populate the ea_guid field in the tagged value tables?

I am using EA 13.5 and Access 2016.

Thanks.

Bill

3
General Board / Upgrade to 13 with Postgres db
« on: December 07, 2016, 04:53:55 am »
Hi all,
If I upgrade my application to EA 13 can I still use the same EA 12 Postgres database? Thanks.

Bill

4
General Board / baseline fail
« on: July 14, 2016, 09:48:22 pm »
Hi all:
We have a PostgreSQL database set up with our EA 12.1.1227 Corporate Edition clients. I was trying to create a new baseline and got the message:

"ERROR: column "bincontent" is of type bytea but expression is of type lo; Error while executing the query"

I tracked this issue down to what I believe is the culprit, the column bincontent in the table t_document. This appears to be where EA stores the global attributes associated with each baseline. Interestingly, I was able to create a single baseline weeks ago for my database because (I believe) there was no data in this table previously. But now that a baseline exists I cannot create a second one because the code fails when it encounters the original baseline data. So as I see it I can only have one baseline in the database. Any ideas other than delete the first baseline?

Thanks.

Bill

Pages: [1]