Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Mario Rodriguez Jaen on July 25, 2011, 09:06:20 pm

Title: Can an Add-in access a model stored in a database
Post by: Mario Rodriguez Jaen on July 25, 2011, 09:06:20 pm

Just wondering, if I create an add-in, would I be able to use for EA models stored in a database?

thanks,
Mario

Title: Re: Can an Add-in access a model stored in a datab
Post by: qwerty on July 26, 2011, 01:46:40 am

Hu? All EA models are stored in a database. EAP=M$Access which is kind of a database.

q.

Title: Re: Can an Add-in access a model stored in a datab
Post by: Mario Rodriguez Jaen on July 26, 2011, 04:07:55 pm

Yes, I need to explain.

I was referring to a model stored in a central database, like Oracle. If the content is stored in a database server, how is the add-in going to behave when I try to access an element of a folder?

For models stored in a central database, I see some delay when expanding a folder. I was wondering if there are any limitations if you need to develop an add-in.

Thanks,
Mario

Title: Re: Can an Add-in access a model stored in a datab
Post by: Aaron B on July 26, 2011, 04:25:26 pm

In general, EA's API should insulate you from any differences at the database level as long as you are not making any direct SQL calls yourself.  I can't think of any instances where you should need to perform any special handling in your add-in based on the repository type.