nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco data base size and versionedProperty qname

amar

Hi,
I have a repository with 180 000 objects : (spaces and documents), when I select nodes in the table alf_node I have 2 300 000 records, i have 180 000 records with my custom type_qname and remainig records ( more than 2 000 000) with versionedProperty in the type_qname field.
I have one version for each document,
could you please explain me how alfresco manage alf_node records and what's the versionedProperty type_qname ( corresponds)
Thank you

Find more posts tagged with

Comments

acis

versionedProperty is the frozen value of a property of a version node. so if you have a type with 20 properties, each time you create a version of a node from that type, you'll have 20 versionedProperty created en alf_node

dwilson

OK, so in my case I've got in total around 100 pieces of metadata for each piece of content in my custom model- so I'm going to have two orders of magnitude more rows in the DB if I have versioning turned on?

Is there any way to version the content but not the properties- in other words prevent the versionedProperty node from being stored every single time?

At this point we're even considering the work-around of adding a changelog textbox as a 101st metadata item. :shock:

Thanks for any help!

acis

I didn't try to change the versioning process so I can't tell you if you can disable versioned properties.