• UUID is reused after deletion?

  • OpenKM has many interesting features, but requires some configuration process to show its full potential.
OpenKM has many interesting features, but requires some configuration process to show its full potential.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
 #53475  by taranu.andrei
 
Hello guys,

I have a quick question.
if we delete a file in openkm, the UUID will also be deleted. The deleted UUID will be used for another file in the future?

What I am thinking:
We have an integration between OpenKM and another application. In the other application, we store history of UUID's files from openkm.
So, if we delete a file, OpenKM will delete the file(also UUID), but in the history table of the other app, the UUID is not changing, so it will be there.
After a while, maybe OpenKM will generate the same deleted UUID, but for another file. Is it possible?

Thank you,
Taranu Andrei
 #53496  by jllort
 
UUID is unique based on a logic that use a timestamp, etc... it is quite difficult ( nearly impossible ) the UUID be repeated. Remember when document is deleted go to the trash ( still exist in the OpenKM repository ), when clean the trash document is definitively purged of the system and totally removed from the database. Only in the table, OKM_ACTIVITY will display information about purged nodes -> history is never deleted.

About Us

OpenKM is part of the management software. A management software is a program that facilitates the accomplishment of administrative tasks. OpenKM is a document management system that allows you to manage business content and workflow in a more efficient way. Document managers guarantee data protection by establishing information security for business content.