Defect #1115

Constraint on resource's guid

Added by Magoni Bruno about 3 years ago. Updated over 2 years ago.

Status:AffectedStart date:09/08/2015
Priority:HighDue date:
Assignee:-% Done:

0%

Category:CATALOG
Target version:-
Affected version:4.3.1

Description

Seems that generating guid with php doesn't protect againt non unique identifier generation (encountered with Microsoft Operating System).
Such problem when creating a new resource's version implies that this one can have got a metadata guid which is already used by an already existing metadata. So one metadata can be attached to more than one resource's version (sic).

To prevent such error's case, adding unique constraint over the field which contains metadata guid could be a good option to keep database coherence. In addition, easySDI should verify such uniqueness without falling down. If generated guid is not unique than easySDI should generate other one until it is unique.

History

#1 Updated by Blatti Yves almost 3 years ago

  • Status changed from New to Affected
  • Assignee set to Magoni Bruno

Hi Bruno !

I faced a similar problem.
I don't think that you have encountered an guid generation problem (you faced it multiple times, seems like statistically too much ...).
My optinion is that we have a problem with Joomla's (or component generator) session system.
If you open two resources or items, the second overwrites session data, and then when you save the first, it may use elements of the second (from session).

Do you think this may be the same origin for you ?

Scenario:
  • Open the new resource form
  • Open another existing resource edit form
  • Save the first 'new' form

#2 Updated by Magoni Bruno almost 3 years ago

  • Assignee changed from Magoni Bruno to Blatti Yves

Hi Yves,

Unfortunately it's not the same origin you mention, as I encounter this problem again today without opening several resource's form.

Bruno

#3 Updated by Blatti Yves almost 3 years ago

  • Assignee changed from Blatti Yves to Magoni Bruno

Thanks for your reply, I'll open an issue for my case

#4 Updated by Mérour Xavier over 2 years ago

Do we have any news on that defect ?

#5 Updated by Magoni Bruno over 2 years ago

  • Assignee deleted (Magoni Bruno)

No more news as no one is able to reproduce such behaviour.
I propose to treat such issue as an enhancement for preventing such error as described in summary...

"To prevent such error's case, adding unique constraint over the field which contains metadata guid could be a good option to keep database coherence. In addition, easySDI should verify such uniqueness without falling down. If generated guid is not unique than easySDI should generate other one until it is unique."

Also available in: Atom PDF