Undocumented command: Repository.Execute

[fwoolz]

Another one for Sparx:

The AI provides an undocumented Repository method "Execute," which allows an automation client to execute a non-query SQL command (such as "INSERT INTO..." I know this works as of 8.0.857, because I just tried it with the table t_xrefuser). Would Sparx consider changing this from 'undocumented' to 'documented', as it provides add-ins with additional flexibility in accessing the EA database?

Cheers,
Fred W

[mrf]

Fred, you know too much. Expect a visit from the lads soon :p

On a more formal note, we do not support or recomend direct manipulation of the database in any form (be it through the automation interface or through a dbms tool). If you're missing functionality, then we'd prefer to provide it through an automation function that can be tested and contained.

The usual disclaimer: we do not take any responsibility for lack of data if you do use Execute() (or an external dbms tool) to modify the underlying database.

PS: As with the custom commands, I would not bank on this undocumented method being in future builds of the automation interface.

[fwoolz]

Mr. F sez:

I PITY DA FOOL THAT USES UNDOCUMENTED METHODS!

...or, more precisely:

PS: As with the custom commands, I would not bank on this undocumented method being in future builds of the automation interface.

That's what I was afraid of.

Cheers,
Fred W

PS: You would be safe if Bob Marley rolled by as well...

[RoyC]

Whether it be Bob Marley or Eric Clapton, I'd still be a nervous posse-member. They might not have shot the deputy, but them deputies still keep on a-dyin'.

I would guess, too, that if I tried to document the undocumented commands, Mr F would lock and load and shout NO MORE JIBBER-JABBER, FOOL! I really would not like that to happen.

[fwoolz]

I trust that with Mr. F and the rest of the Au-Team on board, Geoff and his posse are safe from sheriff-shooting singers. But now I wonder if I need to buy me some protection from The Lads^TM.

[Geert Bellekens]

Fred,

Could you post a code snippet on how to use Repository.Execute to execute sql commands?
Could come in handy sometime.

Thanks

Geert

[fwoolz]

Hi Geert,

Here's the (VBScript) code I used to test out the method:

Code: [Select]

' THIS WORKS 2010-06-15
Repository.Execute("INSERT INTO t_xrefuser VALUES ('ABCDEFG','CCC','DDD','1','2','3','4','5','6','7','This is a test','8','9','10')")
Repository.Execute("INSERT INTO t_xrefuser VALUES ('ABCDEFH','CCC','DDD','1','2','3','4','5','6','7','This is a test','8','9','10')")
Session.Output(Repository.SQLQuery("SELECT Client FROM t_xrefuser WHERE XrefID = 'ABCDEFG'"))
Session.Output(Repository.SQLQuery("SELECT XrefID FROM t_xrefuser WHERE Client = '8'"))
The method signature is:

Code: [Select]

void Execute([in] string SQL);
Both the script output and a check of the (.eap) database in Access indicated that the rows had indeed been added.

I haven't tried commands like CREATE TABLE - yet.  

Fred W

PS: I wish Sparx would give us a sandbox in the EA database...

[fwoolz]

Geert,

Here's the code for a quick test of CREATE TABLE:

Code: [Select]

Repository.Execute("CREATE TABLE u_testtable01 (uID long, uName char)")
A check of the Access database showed that this did in fact create the table with the fields specified.

Apparently the commands for an .EAP file are fed to DAO since DAO error messages result if the syntax isn't right, so command format and data types must be DAO-compatible if your repository is an EAP file.

PS: The modified .EAP file with the added table passes the Project Integrity Test, BTW.

Fred

[Geert Bellekens]

Ah, that simple  

Opens a whole lot of backdoor possibilities.

Thanks Fred.

Geert

[SomersetGraham]

Hi
Here is how I used Execute
[code]
string query = "UPDATE t_object SET PDATA1='All Scenarios' WHERE Object_ID=" + noteElement.ElementID;
            Repository.Execute(query);
            query = "UPDATE t_object SET PDATA2=" + currentUseCase.ElementID + " WHERE Object_ID=" + noteElement.ElementID;
            Repository.Execute(query);
            query = "UPDATE t_object SET PDATA4='Yes' WHERE Object_ID=" + noteElement.ElementID;
            Repository.Execute(query);
[\code]

HTH

Graham

[RodneyRichardson]

Well, Repository.Execute(sql) is still in the API 15 years later (v17)... make of that what you will.

[shimon]

Documented or not, Perplexity gave it to me when I asked him how to update some diagrams that he helped me create via script. 

[Geert Bellekens]

Well, Repository.Execute(sql) is still in the API 15 years later (v17)... make of that what you will.

I suppose that if they removed that from the API, half of the addins will stop working.

Unfortunately this method is often the only way to achieve certain things as they are not exposed in the API (or only as read-only properties for some reason)

Geert