Database Query Restrictions in Enterprise Architect 17.2

[emiliano.davila]

Hello everyone,

We are currently testing the upgrade to Enterprise Architect 17.2 and have noticed some changes regarding database queries.

First, we observed that it is no longer possible to query the repository security tables, such as `t_secuser`, `t_secgroup`, and `t_secusergroup`, among others.

Additionally, the `Repository.SQLQuery()` method apparently only allows `SELECT` queries, meaning that it can no longer be used to execute `INSERT` or `UPDATE` statements.

We have also encountered issues when running recursive queries using expressions such as `WITH RECURSIVE`, even when they are read-only queries.

We reviewed the published change history for EA 17.2 but could not find any information related to these restrictions.

Has anyone experienced similar behavior?

Is this an expected and permanent change in the tool, or is there any configuration that would allow these operations to be enabled again?

Thank you in advance.

Best regards,

[GeordieKiwi]

These are likely to be in response to security issues that were brought to light a few months back

[Geert Bellekens]

Additionally, the `Repository.SQLQuery()` method apparently only allows `SELECT` queries, meaning that it can no longer be used to execute `INSERT` or `UPDATE` statements.

This has always been the case. For insert or update statements, you needed Repository.Execute(), which apparently has been disabled as well.

Geert

[Helmut Ortmann]

Hello,

I also stumbled on the issue with Update/Insert via sql and EA 17.2 (disabled).

Is there a way to set e.g. PDATA3 for a Part which points to the original part (if the part is a reference)? In the past I used sql because there is no API (readonly property).

Ok, I can access with native SQL. For sqlite this shouldn't be a big deal.

Other databases aren't always that simple.

Have someone an idea or experiences?

Thanks,

Helmut

[Geert Bellekens]

Hello,

I also stumbled on the issue with Update/Insert via sql and EA 17.2 (disabled).

Is there a way to set e.g. PDATA3 for a Part which points to the original part (if the part is a reference)? In the past I used sql because there is no API (readonly property).

Ok, I can access with native SQL. For sqlite this shouldn't be a big deal.

Other databases aren't always that simple.

Have someone an idea or experiences?

Thanks,

Helmut

I've sent an email to Sparx support, with my list of all the things I use the now retricted methods for, asking for alternatives.

I have yet to get an answer.

I'm afraid I'll have to switch to native database queries at some point.
Upside of that is that this is much much faster than Repository.SQLQuery, and you don't need to worry about the translation into xml.

Geert