What is the real risk of using Repository.Execute

[dangel]

I have read it is unsupported method and risky to use!!
so the question why and what is exactly the risk?

[qwerty]

a) It is unsupported.

b) You can turn your repository into a trash bin by e.g. executing

Code: [Select]

DELETE FROM t_object

 or

UPDATE t_object SET name=' '.

q.

[Geert Bellekens]

One of the dangers I only discovered recently is that EA only executed the code until the line that contains a comment.
So

Code: [Select]

-- this is my sql code
Delete from t_objectWill actually do nothing as the comment is found on the first line.
In my case it was a bit more devious. I had something like

Code: [Select]

Delete from t_objectproperties
-- where object_ID = 1234
where object_ID in (<selection of object id's>)
and Property = 'Name of TV to be deleted'
The line where object_ID = 1234 was used during testing so I would only delete TV's from one object. So I put that line in comments and then executed the whole thing, resulting in a repository without a single tagged value

Luckily I was executing this on a test environment and not directly into the production repository - no harm done

Geert

[qwerty]

Whoa. What does this tell us? Sparx code has a comment detection which make things go wrong. So most likely Sparx' code itself has no inline comment

q.

[Paolo F Cantoni]

Thanks for the "Heads Up", Geert!    

I presume you reported the bug...

Paolo

[qwerty]

I guess not. As mentioned so often: the method in question is unsupported.

q.

[Geert Bellekens]

I guess not. As mentioned so often: the method in question is unsupported.

q.

No indeed, i did not.
Maybe we could anyway. Who knows, it might even get fixed one day.

Geert