Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: coatie on November 20, 2015, 06:02:19 pm

Title: Orphan locks
Post by: coatie on November 20, 2015, 06:02:19 pm

Hello,

we make use of EA's security feature and I just got curious about the number of entries within t_seclocks. So I ran query below and it gave me a lot of results, means it seems that there are a lot of orphan locks.  Did I miss something wrt my query?

Code: [Select]

SELECT l.entityid, o.Object_id, o.Name, o.Package_Id, u.userlogin, l.timestamp
FROM t_seclocks l
LEFT OUTER JOIN t_object o on o.ea_guid = l.entityid
LEFT OUTER JOIN t_secuser u on u.userid = l.userid
WHERE o.Package_id is NULL

Markus

Title: Re: Orphan locks
Post by: Geert Bellekens on November 20, 2015, 06:11:11 pm

Markus,

I wouldn't worry too much about that unless it is affecting EA's behavior in some way.
There's a good chance orphans like that are cleaned up when running a project integrity check.

Geert

Title: Re: Orphan locks
Post by: coatie on November 20, 2015, 07:57:48 pm

Hi Geert,

no, integrity check does not consider that. So I guess I head for rephrasing the query to a DELETE...

Markus

Title: Re: Orphan locks
Post by: Geert Bellekens on November 20, 2015, 08:49:16 pm

Quote

Hi Geert,

no, integrity check does not consider that. So I guess I head for rephrasing the query to a DELETE...

Markus

Why would you do that?
Are these locks an issue somehow?

Geert