Dangling Proxy connector

[Karan Mundhra]

Hi,

I have some proxy connectors in my database.
These proxyconnectors have a classifier. This classifier when seached in t_connector table must lead to a new connector, which is source.
Basically classifierID of proxy connector  = ConnectorID of the connector from where the proxy connector originites.


Now the issue is that the classifierID of the proxy connector is not existing in the database in t_connector table.


Any clues how can I solve this now /  get rid of the proxyconnector objects?
Also how can this happen?


Thanks
Karan

[Geert Bellekens]

Have you tried a project integrity check?
That is the tool that is intended to solve this type is issues.

Geert

[Karan Mundhra]

Hi Geert,

I have as database hosted for this project. I guess integrity check can run only on EAP.
I would have to transfer the DB to file and then do the check and then push back the eap to DB.


Thanks
Karan.

[qwerty]

No. The check can be run on any repo. Just make sure nobody is actively working during the check.

q.

[Paolo F Cantoni]

Hi Karan,

If the Integrity check (which, as qwerty says, runs on all types of repositories), does not pick them up please report a bug using one of the links below.

It is vital that the internal integrity of the EA repository can be relied on.  That's what we principally use the Integrity Check for.

Essentially, if the IC reports an error, "All bets are off" until the errors are removed...  (if the errors aren't found...  )

Paolo

[Karan Mundhra]

Hello Qwerty, Paolo,

The integrity checker does run on repositories also. Thanks for pointing out.
It also removes the proxy connectory.

Still wondering how it appeared. Tried it on a local setup to simulate the problem but could not.


Thanks for the help!

Regards,
Karan

[Geert Bellekens]

Still wondering how it appeared. Tried it on a local setup to simulate the problem but could not.

That's not difficult. EA works without transactions. If something happens during an operation (such as creating or removing such a proxy connector) then it is perfectly possible that only half of the sql statements executed.
And since there are also no referential integrity constraints (FK's) in the database, this all goes by without a beep.

So you need something like the project integrity check to clean up those loose ends.

Geert

[qwerty]

Unfortunately EA does not do that automatically (like *nix forces fsck every now and then). Even worse: when you start the check EA scares the user how dangerous it could be and you better don't use it. Goes without further saying.

q.

[Paolo F Cantoni]

By the way, Karan,

Although Sparx calls it a proxy connector you'll have noticed it's not a connector (and specifically it is in the t_object table, NOT t_connector).  I've found it useful to more correctly call (and think about it) as a Connector Proxy.  That is, it is a proxy for the connector in the t_object table.

HTH,
Paolo

[Karan Mundhra]

Hi Paolo,

Yes, I am aware it goes in the t_object table. Also it does not appear in the project browser.
Even I think, connector proxy is more sensible name

Thanks
Karan